Seeing "the source is available here on GitHub", "the project was forked and is now maintained as (other name)", etc. after most of these really helps show the difference with Google. Well that and the length of the article, Google has far more deaths under their belt.
this post was submitted on 28 Sep 2024
168 points (90.0% liked)
Technology
58473 readers
3958 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
A forgotten one is webassembly.studio, an in-browser IDE for creating WASM projects with way less pain than other methods. It got discontinued the year I needed it for my school project. It was open source but I failed to rehost it myself and public mirrors only appeared after I spent days trying to make Emscripten work, tore my hair out over WebGL and then finally painfully built the whole thing with CSS (and a bit of JS; yes, it was indeed a disaster).
Do you still use WASM? I've been exploring the space and wasn't sure what the best tools are for developing in that space.
Nope. But I guess a mirror of WebAssembly Studio would still be the best starting point despite its slow development lately. The WAsm plugin for VSCodium was broken for me too.
Note that unlike JS, WASM won't run from file:// URLs; you need to run a local http server or commit to an online repo to run your code. There might be an about:config option to change this but many IDEs (incl. WA Studio, presumably) come with servers for this reason.
Imagine my disappointment when I realized "Firefox advance" wasn't for the Gameboy advance :(
Twenty things Mozilla the company killed and they didn't mention ITS OWN NAMESAKE APP. It's didn't 'evolve' into Firefox: they split the baby in half and cut away the connective tissue.
Seamonkey is still kinda alive.
I felt the firefox send death, used all the time to share quick files with friends, thankfully I discovered litterbox after they killed it.
I used the Notes quite a bit and thought it was a mistake to get rid of it. People pay for notes and tasks related sync services, so it could have been a revenue source. I also miss Firefox Panorama
Panasonic created their own version of firefox tv to use for their tvs
20 dead Mozilla and Firefox products
Those are rookie numbers!
--A single Google product manager, probably
Honestly a number of these were abandoned for reasons that are fair enough.
Additionally, lots of these are open source and either have been or can be forked.
view more: next ›