So it's a Hackintosh?
Hackintosh refers to doing things the other way around: running MacOS on non-apple hardware. So no, this is not a hackintosh.
Readit NewsKwantuum commented on FrameBook fb.edoo.gg... · Posted by u/todsacerdoti
Deleted Comment
Kwantuum commented on Fabrice Bellard Releases MicroQuickJS github.com/bellard/mquick... · Posted by u/Aissen
https://dorey.github.io/JavaScript-Equality-Table/
https://www.reddit.com/r/learnjavascript/comments/qdmzio/dif...
or anything that touches array ops (concatenating, map, etc…). I mean, better and more knowledgeable people than me have written thousands of articles about those footguns and many more.
I am not a webdev, I don't want to remember those things, but more often than I would wish, I have to interop with JS, and then I'd rather use a better behaved language that compiles down to JS (there are many very good ones, nowadays) than deal with JS directly, and pray for the best.
Both of the things you quoted are basically gone in practice, you just always use const/let and always use triple-equals for equality comparisons and that's that. Most people that write JavaScript regularly will lint these out in the first place.
OTOH I think JS has great ergonomics especially wrt closures which a number of popular languages get wrong. Arrow functions provide a syntactically pleasant way to write lambdas, let/const having per iteration binding in loops to avoid nasty surprises when capturing variables, and a good number of standard methods that exploit them (eg map/filter on arrays). I also think, though a lot of people would disagree because of function coloring, that built-in async is a great boon for a scripting languages, you can do long operations like IO without having to worry about threading or locking up a thread, so you get to work with a single threaded mental model with a good few sharp edges removed.
Kwantuum commented on I think nobody wants AI in Firefox, Mozilla manualdousuario.net/en/mo... · Posted by u/rpgbr
I am a regular Firefox user; it is literally the tool I use most often during my working hours. I like it more than Chrome.
Firefox is steadily losing market share, and any attempts to do something about it are met with negativity. The 2-4% of users who use it care about their privacy. But they are not being deprived of it; the AI tab is optional, and no one is removing the regular tab. (Of course, it would be better if they allowed the integration of local models or aggregators, such as Openrouter, Huggingface...)
Meanwhile, developers continue to ignore Firefox, testing only Chromium browsers. Large companies are also choosing the Chromium engine for their browsers.
Perhaps if they implement this functionality conveniently, more average users will use Firefox.
I've had to stop using FF as my development browser because it chokes on large source maps. I used to find lots of issues in our web app that were only ever tested on chromium browsers. I don't anymore because the devtools are unusable past a certain point.
It's not a realtime system kind of thing where the debugger would change the behavior too much... It's possible with enough engineering work, but nobody has put that work in, in fact they had a debugger for some staging envs that they deleted. Lately they keep adding more red tape making it hard to even run something locally, let alone attach a debugger.
I guess you can attach a debugger for unit tests, but that's not very useful.
> I guess you can attach a debugger for unit tests, but that's not very useful.
That is in fact incredibly useful
Kwantuum commented on Unexpected ways memory subsystem interacts with branch prediction johnnysswlab.com/unexpect... · Posted by u/r4um
I'm pretty sure the following optimization is invalid, since a is not a bool array, but one of positive/negative numbers (see top of article):
> You can use arithmetics to go branchless.
if (a[i] > 0) {
cnt++;
}
cnt += a[i]Surely this was meant to be cnt += a[i] > 0
I think many commenters supporting the "kill my app" behavior do not understand how bad using the affected devices can be.
The reason I first discovered "don't kill my app" is that my apps would close as soon as I switched to another one, in most cases. For example if I used maps and switched to a call / browser tab / Telegram chat, when I got back to the map the app would reload. My search would be gone, and I would have to set my destination again.
I hope you can agree that this is terrible user experience. If I wanted to save battery, I could have just closed my apps manually, I don't need my phone to take the initiative.
The most egregious problem caused by this that I've encountered is an almost complete inability to use email 2FA on websites because my phone will kill the browser as soon as I switch to my inbox, and when I go back to the browser I'm back on the login screen which will generate a new one-time-password and make the one I have in my clipboard worthless. I've also encountered the exact same problem with 2FA using an authenticator app, though since the codes are valid for ~30 seconds or so, if I manage to enter my credentials fast enough or they auto-fill, at least the code I copied is still valid.
Kwantuum commented on How to rewrite classes using closures in JavaScript gaurangtandon.com/blog/ja... · Posted by u/gaurang_tandon
There are several points in the article which are just plain wrong:
- no private properties (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...)
- no readonly properties: You can use a getter. Or define the property as non-writable, the syntax isn't nice but in my opinion it's still much nicer than what the article proposes.
Some of the points are just a matter of taste ("this" is awkward)
There's the implementation itself which forces you to use non-idiomatic code for no good reason or benefit (Class.init instead of new, just why? You can absolutely return a constructor function there while preserving everything else)
Doing what the article proposes also destroys the ability to do instanceof checks because the prototype of instances is not set (can be fixed), and inheritance is severely limited if you want to preserve any of the purported benefits. You might say that inheritance is actually not a good thing and so it's a feature, not a bug, but if that's your opinion why are you trying to mimic a class?
Kwantuum commented on Minecraft Wiki has decided to leave Fandom minecraft.wiki/w/Minecraf... · Posted by u/unleaded
I remember in 2009 or 2010, when I first came across Minecraft. It was not hugely popular yet, but it already had quite an active community.
I played quite a few hours of the game, both alone and together with a couple of friends.
One day, after a couple of weeks or something, I learned about a crafting wiki that told you how to craft different items.
At the time, at least for me, it was not clear how you figure out what items you can craft and what items need to be combined in what patterns to craft those new items.
So for me, that crafting wiki became quite essential.
Maybe other people were figuring out how to craft things by trial and error? Or maybe there was something in the game that told them how to craft specific things?
There was not. There is now but for the better part of a decade it was just... Something you were supposed to have learned from a youtube video or a friend or something.
I'm mot sure why you're replying this to me. Did you mean to respond to someone else? It seems to be formed argumentatively but follows what I was already saying.
Pretty sure they're just replying specifically to
> you still have guilty parties going free anyways since the wrong person is convicted
which is a non sequitur.