These days it’s very common to write whatever code you want, and a formatter automatically rewrites it to conform to the projects rules during precommit.
Which is great because it allows you to focus on intent instead of format, and completely avoids any team disagreements or change rejections for trivial bullshit.
We in this forum are a specific type, few use lemmy, and few invest in Arm directly.
SpaceX and Arm aren’t comparable, f.e. I know a college student investing in Space X, as well as an Elderly man, a cousin of mine who works in marketing, etc. It’s normal joes who want in. That never happened to Arm, and I’d be surprised if it ever does. It won’t be mainstream. I don’t know anyone personally who invests in Arm other than myself.
I’m talking about norms and sensationalism, not the state of a technology.
Notably ARM was not mainstream when it IPOd either, meaning it was a safe® bet at the time.
Most IPOs have become sensationalized to drive up interest, which is terrible for everyone except a select few.
Actually it technically does get irradiated by neutron activation, but the half life of Nitrogen-16 is only 7 seconds, so by the time it reaches the filters it’s already poof decayed away. (Very small amounts)
I’ve never owned a flip phone that I couldn’t plug in and swap the battery with a new one without it turning off. If that wasn’t normal with your phones I’m not sure why, maybe different circuitry?
Regardless making devices easy to repair, and thus open and maintainable was what I was getting at.
Codeberg / Forgejo and Tangled are my favorite options. Tangled because while it is VC backed, the open source and federated model are well thought out. If you haven’t read the source code I highly recommend it, it’s genius.
Just make hot swapping batteries normal again like it used to be.
Ironically somehow AI is making disabling JS better nowadays, because text/markdown is becoming normalized, so receiving a pure text version of a page is a thing again.
The pain I felt when I cracked my 12” display still echoes in my mind.
I would use this for streaming games from a wired PC to a device that’s wireless. Not having to run a wire is magical.
It’s not common knowledge outside of dev circles tbh, your advice to blocks ads though is legit. You don’t deserve those downvotes
I wouldn’t call them different browsers, more like skins or “chrome”. All iOS browsers are built on Apple WebKit. This essentially makes all of them reskinned versions of Safari.
Sure they may have some clever UI, accessibility, or platform specific functionality. But they are nothing like any of those browsers on other operating systems.
And then someone posts your tiny hobby site to a popular forum and you get hugged to death. There are plenty of people who say they don’t like centralization (which is fair), and a lot who mention not using Cloudflare (which is fair), but there exists plenty of great reasons to use the tech whether you like it or not.
Instead we should be focused on what the alternatives are depending on your needs, recommending solutions to actual problems, rather than just yelling at the sky.
Those are just a few I’ve used in the past in enterprise settings, but there are a lot out there.
I tried Kagi, and hated its results so I cancelled. I don’t understand the love for it I see online. I enjoy self hosting searxng, where I can configure it for myself or family, for our needs. I also am a fan of marginalia, both which cost me nearly $0 a month, and work wonderfully. I’d rather invest in supporting them through time and money than a corporation like Kagi.
A source map is a file that maps minified code (such as ES5 or any Javascript) to the original source code (e.g. ES Modules, Typescript, etc). This makes it easier for developers to debug problems. Source maps aren’t unique to Frontend web development, but the scenario in the article is.
Imagine if I asked you to fix an English subtitle typo in a film that was subtitled in a language you’re unfamiliar with (maybe Mandarin). At first you wouldn’t understand anything in the film, other than the pretty pictures, and struggle to find the correct segment to fix. But later I provide you with an English subtitle file and timestamp for the movie, so you could go find the actual place to fix the issue. This is kind of what source maps are like, they allow us to map from compiled code to the original, making it easier for us to debug and context switch less, saving a lot of time. They also allow us to better understand the original intent, since it’s the actual source.
The source code is the original source at the time it was recorded for the Apple App Store on the web. But will quickly become out of date as changes are made frequently by Apple.
When I was younger someone deleted a save file of FFTA I had clocked over 400 hrs on (it was a genuine accident), and I was devastated.
I then proceeded to play again with over 1k hours. Might be one of my favorite games ever made.
Phat DS can play them too, don’t forget about my thicc boi
I took one of the broken ones from my office, repaired it, and now it allows my dnd campaign to see the DM and all the other players reactions when playing remotely.
While I don’t know this is the case, I can say from experience that in large enterprise organizations compliance departments will and do actively prevent the release of features and even commits if they don’t comply.
While that’s not an excuse for challenging them, I could definitely see a stressed out mid level just trying to make there manager happy and move on with life.
I hear you, but these are solve-able human problems, not code problems:
Manager: Jose revert your commit, thanks. Jose: okay, it’s been reverted, I won’t do that again, thanks for explaining to me why exactly what I did was the wrong thing to do.
I’ve had this exact conversation about this topic at least a half dozen times over the last decade.
When it comes to legacy code, almost all auto formatting tools I’ve used allow you to ignore whole directories and files, which can be very handy for legacy areas of the codebase not yet ready for this transition.
As for scenarios where large rewrites are necessary, it’s best to separate from any actual work, so the blast radius is focused, and that commit can be marked properly using .git-blame-ignore-revs which completes fixes the history issues that are common amongst those who don’t know what they are doing.
Definitely a painful process it can be, but it’s better to fight this battle than it is to try and get 1,000 humans to agree on something as vague as “style”