I bet code reviews with markers are fun though.
205 karma · joined February 22, 2022
I saw this as a JS developer who scarily runs npm installs multiple times a day.
With the latest MacBook Pro it feels like they're back on the right track. Heck they dropped the magic bar.
The issue with replaceable components is that they're often at odds with performance. If MacBook had user-replaceable batteries we simply would have less battery OR a thicker and heavier and more expensive computer. Literally you cannot have all.
Memory/SSD sticks take more space and cost more than a soldered chip (and they earn Apple more money, shhh)
It's a compromise though, I get it.
- traveling with covid
- needing to extend a visa after 20 days in the EU (Ukraine is not a Schengen country so he just entered) even though it’s 90 by default.
- thinking it “works in 150 countries” without limits
- attaching a sob story and unnecessary medical details about how much he needed for this to not happen
Since the lockout happened at least 17 days after he got the fever, he most likely does not have covid and can definitely fly back to the US, just like he flew with covid to Spain.
But of course that’s more inconvenient than just blaming someone else.
Side note: there are also GUIs for the terminal, they’re fine.
I never commit from CLI and have been using GitHub Desktop for years (it works on any repo/remote). Selecting individual files, patches, or even lines is a breeze. I usually make a bunch of changes, then pick, commit, branch, repeat. Every branch is based off `main` and can be pushed independently. Any leftover will just be dropped (any logging/testing lines that I never picked, for example)
Using a UI makes it easy to review your changes before you commit them, there’s no way you can review (and pick or discard) your 100-lines 5-files changes effectively on the command line.
GitHub Desktop is quite limited and I hope it stays that way, I still use the cli for operations other than commit and checkout.
> trusted Google users
> (after manual review)
> already exists and works on Google Maps
Even the data collected from a personal blocklist would be useful for them, without explicitly reporting sites, but again they just don’t care.
They’ve been in the business of parsing websites for 25 years, surely they can tell ad-infested spam websites apart from good ones.
They already exist. We're living in the future and/or a joke.
This and Russia turning the yellow arches sideways calling it Uncle Vanya make it feel like we've entered Los Santos.
The iPhone 11 Pro already came with USB-C, so that already did not happen.
> came off looking cheap
I don’t think anyone really cared. Who bought Apple will continue buying Apple, this move has zero downsides for Apple. We need to leave the tech bubble to see it.
The comment said "invented the modern slab-of-glass smartphone industry".
That's it, that's true, there was no "slab-of-glass" smartphone industry. The comment did not say "invented the smartphone industry" — all comments after it are just unrelated.
Yes there was there were smartphones 10 years prior. No they were not slabs of glass.
Wasn't that debunked? Just look at what happened to people who slept in a cave for a few days, they came out of it having no idea of how long they were in there, even if they were somehow conditioned by others who guessed their own time. If the body had an internal clock, their estimation would not be off by 17 days out of 40. That's some serious mismatch.
https://www.insidehook.com/daily_brief/science/french-cave-d...
In Norway in December people wake up "in the middle of the night" because sunrise is at 10am: Humans can adjust easily to this stuff, it's just that we like to sleep "late" (as defined by the clock)
Tiny projects are fine, but they don't all need to be posted to HN.
Someone marks your business @domain emails as spam, now your account is locked. Why would you put yourself in this situation? Just, don’t.
Reddit is its shitshow and I ended up installing Apollo. This is not Safari’s fault.
I’m still waiting for regex lookbehinds, a ES2018 syntax that I can’t use. Literally Safari does not execute the whole file if you use such regex literals.
With so many 10x full-stack developers who're just looking to get sh done and clock out, it can't be otherwise. If managing a server becomes just another bullet point in a developer job, this is exactly what we get.
Sure I can deploy stuff, but you shouldn't trust me. Unfortunately many are not so honest or even aware of the complexity (unknown unknowns).
The locking is already there, but the operator is chosen at the activation so that Best Buy can sell one model for any operator.
So the blame is actually Apple’s for blindly allowing this behavior, Best Buy’s for not advertising it, T-Mobile’s for allowing this through MNVO’s, and Google’s for not knowing that this happens and not allowing unlocks.
And they said my Node dependency tree was a mess!
I bet Americans love picking a $80,000 hospital bill over a $90,000 one.
Government decisions, done well, go far beyond what voting with one’s wallet can. Oftentimes the consumer is just squeezed out of the equation and everyone’s price will follow.
One company decides to do away with replaceable batteries and you will say "let the consumer vote with their wallets." Then everyone does the same and the user can no longer vote.
What we get is instead a mountain of waste that everyone has to pay for, indirectly, forever.
That’s why they do it, but what they’re doing is essentially rejecting the request. If it’s a question, sure, but if it’s a feature request or worse yet a bug report then moving to discussions is bs.
You mention the only worthwhile exception: sums and other 3-character operation.
If you’re using reduce to construct objects you’re just better off with a for loop. Having a random awkward named function that only makes sense when plugged into reduce is not any better than just have a function that includes the loop itself:
- newArray = array.reduce(operation, [])
+ newArray = operation(array)
The problem is that reduce can do anything and most people use it to do anything. It has no advantage over regular for loops unless you’re proficient with real functional programming (if you use forEach() in JavaScript, you’re not)
> With both, you only have to write what happens to one element, and it will happen to the whole collection. This makes code easier to read.
Filter and map are ok. Filter, map and reduce are not, at least not in JavaScript. Try writing the equivalent for loop and you’ll find that it’s just as simple to follow.
Mind blown :o
Anyway it made sense at the time, it’s just unfortunate. The only redeeming part is that in Indonesian it’s actually spelled Jawa so it doesn’t affect locals too much