It really looks pretty interesting and helpful for me and a lot of persons out there! :)
But one thing: If you record demos please try to setup your mic correctly. In the demo you've shared the audio is pretty often clipping (which does not really sound great/ sounds unprofessional)
There are a few (unofficial) moddable games if you look into the homebrew scene. But for this you need to have a Switch that is capable of running unofficial code (either old Switch with a softmod or a Switch with a hardmod)
If you have such a Switch you can use a tool that overwrites/unions the content of the game cartridge with content of a folder on your SD card. That means you could add some files (e.G. maps) into the game.
From the top of my head you can definitely mod the Skyrim Switch version as well as the Star Wars Jedi Knight Games (at least these were the two games which I've played around it). But I am pretty sure that there are Mods for the mario games.
Depends what you mean by "moddable". There are plenty of games that allow for user-generated content, like Super Mario Maker 2 or Baba Is You, for example. That might not be as moddable as a system that lets you run arbitrary code, but that seems more grey than black-and-white, to me.
From my point of view it was really a game changer. The first time debugging and understanding web-applications became accessible. Probably all browser dev tools were inspired by this tool
Firebug is the reason Firefox broke IE’s crown. On one project we had management tell us specifically not to support Mozilla. Fuck you man. We get the software running on Mozilla first because it’s the only place we can debug properly. Then we fix whatever IE bugs are left over by dead reconning. We’re still going to be Mozilla first, we just won’t tell you about it anymore. And you just lost some trustworthiness so good luck convincing us of something difficult next time.
I still think the Mozilla team did Firebug a dirty by reimplementing what was an inferior version instead of bringing it home.
Exactly that. When Mozilla started reimplementing it, it seemed somehow error stack traces started breaking for both firebug and the horrible builtin developer tools
That's when we switched to Chrome for debugging, and only come back to Firefox to debug endless loops and stack overflows (because their Javascript VM is still better at being able to suspend/trace those)
Well, Mozilla itself was the result of a failed attempt at a rewrite. Jamie Zawinski decided that being a bar owner was a better career option shortly after that experience.
It’s hard to tell with autodidacts if they really got pissed off about something or just needed an excuse to deep dive into something completely unrelated, and I would definitely peg him as one.
Firefox 1(?) already had the error console, which told the _correct line_ where the error happened with more meaningful messages. Unlike IE where the message was something like `Unknown error at line 10203` when you had only a big HTML table and some inline JS.
That was already a big improvement, but then Firebug was another dimension.
> Probably all browser dev tools were inspired by this tool
Joe Hewitt begat DOM Inspector[1], which, after Hewitt left Netscape, begat Firebug (originally "FireBug"), and then pretty much every other Web developer tool began as an attempt to create something that could compete with what was available in the Mozilla ecosystem.
It certainly changed my life when I saw it for the first time. In fact, I do remember the exact situation when I was shown Firebug, and my realization that my live as a (then) frontend developer would change for the better from that moment on.
I can't even comprehend how anybody was able to do Javascript development pre-Firebug. I dabbled in client-side web development a bit in the early days of IE and found that the default behavior of a Javascript-enabled page when it encountered an error was to render a blank page and not log or report an error anywhere. I immediately retreated back to server-side development and didn't go back for years.
I taught myself programming with ASP Classic (VBScript) completely unaware of debuggers and it was normal to dump variable values to the output to try understand what was happening.
I did the same with PHP and initially the same with JavaScript.
However, once I learnt how to debug in Chrome’s dev tools, the idea of working without a debugger for any programming became unthinkable.
Actually, console.print was a later addition - when I started looking at Javascript, you could only do alerts, or you could call "status" to display something in the lower part of the frame. And if you accidentally alert()-ed inside a loop...
Still, I can't comprehend how you could develop anything in Javascript with just console.print either. You have my respect and admiration.
I remember there being a console window in the late 90s... don't remember what the full functionality was at the time however. Maybe it only showed warnings/exceptions?
It wasn't too dissimilar to developing a gui app, you could print to the console, raise a dialog, or if you wanted to be fancy implement a log with a window or pane to show them. Logging is what I use today for backend systems. It is usually enough, only breaking out a debugger once or twice a year.
Firebug enabled me to be a "real" web developer. Prior to that I was just slinging ASPX files with no real idea what I was doing. This tool was the gold standard for powerful developer tools that aren't overly complicated.
7 years seem to be a long time, but for something that operates on such a low level it isn't. Rust also exists for 12 years now, but got the most traction in the last 2-3 years.
From my point of view wasm is currently in a state where a lot of companies and people are learning. Most of the toolchains had to mature before the broader mass of developers (who have an interest in this technology) took a look into it.
Yeah, you are right, it is lesser used than e.g JavaScript, but tbh it also has a different target audience. You probably can build UI by using wasm. But why don't use JavaScript, which is way more comfortable and has a bigger community around it? (Unless you have some specific needs)
As a web developer you don't need wasm right now. If you are doing some lower level work (like trying to run AI models/training) and you really need the performance, then wasm gets pretty interesting.
Most of the cool wasm projects I've seen in the past few months/ years were open source ports of games or emulators compiled to wasm (like Doom 3 ), which really ran very great. And my guess is that the broader development community is currently doing exactly this: they are playing around with wasm to learn for what use cases wasm could be a great fit.
(more known Wasm users are for example Figma or Google Earth. Iirc I've read that BBC is currently exploring if they can use wasm for their media players)
Just a side note:
Iirc Spotify does not use Electron - it uses the Chromium embedded Framework. It is kinda the same as electron (it gives you an Browser) but instead of JavaScript you have to use C++ (or a wrapper around the library in you favourite language) to implement the Backend side of the app
I completely agree with you, but I a small thought about public key authentication.
Today more and more people without a background in IT which got in the "Web3"/Crypto ecosystem get in touch with public key authentication mostly used with wallets like Metamask. It get's understandable and usable for the average user.
I don't see what that would get me that I wouldn't already have with Sign In With Apple, other than not being tied to Apple, which is one of the most important features of SIWA: if something goes wrong, there will be an ultra-annoying hard-landing customer service procedure that will, ultimately, restore access to my account.
But one thing: If you record demos please try to setup your mic correctly. In the demo you've shared the audio is pretty often clipping (which does not really sound great/ sounds unprofessional)
Otherwise: Good luck on your journey!