skysight-inc/HackerNews huggingface dataset:
Shared libraries just don't work anymore. That's one of the reasons behind Go and containers.

That way, the users always have working applications. Some applications may take more time to be up to date with their dependencies, but at least some of them can be updated asap without worrying about the others.

For example, I use Debian 10 stable on my laptop, on which I installed Snapd. I then installed Firefox with Snap, and I can be confident that Firefox will have the latest security updates, while keeping the system stable (some parts of the system are probably unsecure, but at least everything still work, they will be updated later)

Although, I would like to point that, while the storage space issue is solved with current tech, the bandwidth is still an issue when on mobile data.
> Goodbye, Clean Code

You mean like with the invention of the abstraction/hack called hooks?
> No, the role of the file system is not to track how changesets are organiced into branches.

Oops, we just got a little bit more feature requests for a VCS than "CRUD changesets and files".

But this isn't an answer to my feature request, which was the ability to merge changes.

> Similarly, patches are only relevant as an external interface of the VCS

Why? If they're relevant as the external interface, maybe this means they model the problem better than snapshots, and should therefore be used as the implementation.
A misunderstanding then. I just meant the difference between big cities and the rest, similar to Paris/rest of France.

The difference you meant was between Spain and Japan. Only 14 km of sea separate our mainland from Africa, with little boats full of desperate people crossing every day. Also we have two towns in continental Africa with land borders with Morocco where border barriers are sometimes just rammed.

But that's just the most dramatic side of it. Most immigrants simply cross the borders as tourists and stay for work. I guess Japan is a little different.

FWIW, Madrid is very safe at night. Only a few neighborhoods, far from downtown, are dangerous.

Edit: immigrant, note taken. Inmigrante in Spanish.
> You either make money from your users or off your users.

I encourage you to have a broader perspective, since this statement isn't true.

E.g. let's examine what Dr Feinberg (who current leads Google Health), oversaw at his last job (see link below).

tl;dr - They gave free food to some people with diabetes, which was better and cheaper than giving them drugs. This was not just free PR, etc.

https://www.hcinnovationgroup.com/population-health-manageme...
Ok, that makes sense. Even when restricting numbers to reals with finite symbolic/program definition, comparing two such reals requires an unknown and unbounded number of their digits to be computed. If two symbolic representations define the same number, but it isn't obvious, a complete digit comparison will never end. Got it.

Thank you!
Are we talking about the Darcs version < 2 merge algorithm or the merge algorithm in current darcs?
I'm no lawyer, so I was trying to not argue on those grounds, however:

What he did seems to fall under modern interpretations of malice aforethought/what it's morphed to (see page 428-429; ctrl-f "recklessness" if desired).

https://scholarship.law.duke.edu/cgi/viewcontent.cgi?article...

It wasn't premeditated, so it seems like second degree murder, doesn't it?
I was under the impression that HIPAA applies to anyone in possession of private healthcare information (medical information tied to personally identifiable information)
I am not sure if I'd call that terminal system anymore useful that those futuristic interfaces where everyone is moving screens around with their hands, headsets with contextual information overlaid atop objects, etc.

They ignore:

1) Usability and ergonomics
2) Privacy implications
3) Technical feasibility
4) Operability in adverse conditions
5) Health effects

I could list more. Also, why do these futuristic interfaces have so much pizzaz, its no less decorative than say victorian frames with french curves. Instead, we have 45 degree lines and chamfers. WHY!?

The entire sci-fi aesthetics throw away what we know about the world, pragmatism and functionalism. Instead, sci-fi aesthetics focus on what looks cool. If future is full of this kind of interfaces, devices and aesthetics; I don't want to be part of it.

I also understand the fiction bit in science fiction. This is a collection of ideas imagined and not supposed to be practical. That's fine and treat it like Harry Potter or any fictional world. But, when you start desiging real things with consequences (such as human-machine interfaces where astronaut's lives depend on), I have a problem with that. Marketing is not the language of nature and decoration is a crime.
Snowpack looks like it works with any 3rd party module, doesnt it? It looks like vanilla-js is more of a jquery style lib + optional addons?
Take a look at Figure 3 in the Performance section of the BLAKE3 spec: https://i.imgur.com/smGHAKA.png. That graph doesn't account for differences in the tree structure, but it compares the performance of both with AVX-512.
Well the reality is, some developers of these complex software complain how their software ported to alternative OSes is difficult to maintain even when the BSD devs would offer to maintain it, which is why the BSDs are always on their own here in terms of porting, testing, packaging and updating the software in question.

For example, Chromium. Any BSD developer would know that attempting to upstream their port there is dead in the water. AFAICT, They Chromium devs only care about Win, Mac, Linux and nothing else. Likewise for Firefox, which is why the BSDs don't get official releases.

I feel some sympathy for OSes like the BSDs that for "some" software they are limited by the arrogance of other open-source maintainers who would rather go for maintaining the convoluted distros and testing with a huge disintegrated software-stack than testing a single unified OS which the BSDs maintain themselves.
Well I guess Benedict Cumberbatch is really in trouble.
Google One gets you 1 year of access to human support for a year so apparently not that hard. I'm sure many people would rather pay that amount just to get their ban reviewed rather than lose their existing email, chat, photos, files, and phone number. The 3 other ~1 trillion dollar tech companies all have customer support without issue.
How about just paraphrasing or echoing what they said? Like:

"I understand that you have difficulties figuring out how to acknowledge what others tell you without necessarily agreeing with what they said. In particular you find that nodding is problematic because of its ambiguity, and you are therefore interested in hearing how other people would deal with this issue."

Have you ever read any Marshall Rosenberg? He's all about that.
This is Google, Facebook et. all’s argument for not doing any content moderation, customer support, etc: “it’s hard”
I'm not so sure. I have a credit card under a completely different name (by accident).
PSA: 500 acre = 2.02 km²
Yes it does actually work and has for decades. The poster is either confused or doing something different, I expect.

The specific notice mentions rust dependencies. Rust does not have shared libraries, so a Rust [security] update means all rust binaries must be completely rebuilt. That seems to be part of OpenBSD's concern, and perhaps this has "triggered" the poster.

user blackhaz random forum post found:

> mariourk, you're definitely not alone. The same breakage happens to FreeBSD desktops as well. I have been vocal around the forum a few times about this. Not every desktop user wants to upgrade all their packages every X months. The way the default repositories are structured, the upgrades are forced onto users. I am a huge proponent of using application bundles, like on Mac OS, as quite often those upgrades break complex desktop apps too. I don't mind upgrades but sometimes I need to stick with a specific version of software, or roll back after something went wrong, and if it came as a bundle with its own dependencies, it wouldn't have to depend on other stuff that is being "force-upgraded" periodically.

So his complaint is about the way FBSD handles updates; he is generally incorrect about shared libraries; and his comment is completely OT for this thread.
You're talking about account recovery, not 2FA. A website can use my phone number for account recovery even if I'm not using SMS as 2FA.

I agree with everything you said about SMS for account recovery.

Account recovery that uses a phone number is weak. There was a paper on HN this week that detailed this.

However, if we are going to compare SMS 2FA (I.E. password plus code sent over SMS) against just password, SMS 2FA wins. In both cases I need to steal your password, the SMS part is an added challenge although it's easier to bypass than many people want.

Given SMS 2FA and any other 2FA option, SMS 2FA loses.
> What you are proposing is to add another “number” to types like int and float that results in the program crashing whenever you try to add it to another number.

There's already division by zero and NaN to trip you up in IEEE754.
This isn’t history, the relevant question is what shared libraries are for, not what they were intended to be for.
There has been an uptick in Google taking more seriously the various laws about collecting, maintaining, and selling data from minors. Lots of effects with YouTube and advertising and here apparently mail as well.

Likely they already knew but are now doing the proper self regulation in fear of or under threat of regulatory action.
Somehow Amazon, Microsoft, and Apple all manage to maintain real human tech support at FAANG scale. Yet the online-first tech companies can't seem to achieve the same. I wonder why that is?
> DRY is about not repeating requirements in code.

Exactly! A lot of developers, even experienced (and I would include the OP, even after his supposed lesson) seem to not get this: duplication is only bad when what is being duplicated MUST behave the same by definition (i.e. if you change one but not the other, the other would've become broken as its definition would still be the same as the changed one). Otherwise, two similar or identical codes are NOT duplicated in a way that violates DRY, they are just coincidental - as they might become different later - so the "duplication" in this case must NOT be removed (but perhaps a smaller portion of the code might be duplication of definition, which should be then extracted and de-duplicated). It really isn't that hard.
Is the shared library issue actually related to this? In the OP they are talking about a Rust upgrade which is presumably only a build-time dependency.
I've humbled and have been humbled before because sometimes what looks like an ugly, unclean solution is the correct solution. There might be weird edge cases in the system that you catch, but the person doing the rewriting doesn't see until they push the code out and it breaks something in an entirely different part of the codebase.

That's the biggest reason why you should always, always discuss those changes with your coworkers first instead of going cowboy on it.
>In fact, no finite amount of computation will guarantee that we will be able to tell whether x=0 or x>0

Hmm, I'm still stuck at this assertion. Why can we not assume the number is finite?

If we assume an infinitely long number takes an infinite amount of time to read, can we not also assume it must take an infinite amount of time to write? If we only have finite time, can we not assume all numbers given to the function in that time are finite?
For one, a personal domain is less secure than a gmail.com domain. There have been quite a few targeted hacks, like Mat Honan or any number of crypto-holders, where a personal domain was socially engineered to be transferred to a new registrar (or password reset on existing registrar) where the attacker controls the MX records, thus your email, thus your password resets.

It’s much harder to transfer gmail.com, office.com, etc
How do people find that offensive?
Its the IT job to provide security without having to inconvenience the user. you can't just add extra layer of inconvenience for the sake of security. Your ultimate goal should be to provide security without adding additional inconvenience to the user or without having the user to notice it at all.
The downside I see with go's error handling is that you can forget to check. With rust, if the function being called returns Result, you have to deal with the error (even if dealing with it just means propagating it out). Missing error handling is such a common source of bugs that go really turns me off here.
That's the thing that perplexes me?

People buy internet connected cameras and microphones for everything from their phones, to their tv's, to their door bells, and then they get upset that their activities are law enforcement accessible on whatever company's servers? I mean, what did people think would happen? That's just the natural way to use that data. How else would such data be used? Maybe to find workman comp fraudsters? Could be used pretty liberally in family courts? Once non technical people begin to realize the data is out there and family court accessible. But it's not like it's gonna be used to get you your next promotion. (Maybe to prevent you getting your next promotion, but that's another thing entirely.)

For me, it just sounds like a really good reason not to be buying cameras and microphones and slapping them up all over the place. When people come to your home, they should feel they can speak and act freely. Especially since they won't be able to do so in public much longer.
I mean, it is a key advantage, on ArchLinux. If you don't have a rolling release, it's pure pain: you're often just stuck with old versions of software which aren't any more stable than the current stable release.
Focus on Conversion, Not Traffic
Why are they “wrong at a fundamental level”?
I'm somewhat surprised Google hasn't taken the old Microsoft route of just charging per call for support on their free accounts. MS used to be $300 way back IIRC. Google could probably charge $500.
This works if you have a stable ABI, but breaks when libraries are written in languages that don't have a stable ABI (in Firefox's case, Rust). Then even a simple recompilation of one package breaks dynamic linking.
I'm not entirely clear on what Nextcloud is. Is it meant for teams/organizations? What does the author mean by "Google Contacts → Fastmail → Nextcloud Contacts"?
Yup, the upfront effort to come to an implementation is like 90% of the work. Refactoring existing code is a lot easier than juggling product, design and technical requirements into a functioning solution. All the moving parts are already there to look at.
The point isn't to stroke your teammates' egos. It's to find out why the code is written that way, and to build consensus around a different way of writing it. Consensus building is a great way to improve the cohesiveness of the team. It lets teammates operate with a set up implicit, shared assumptions, which means they can spend more time on business problems and less time on these kinds of discussions.

Generally, lone wolves worsen the team dynamics, because they reduce team cohesion.
From the US perspective, other countries YMMV:

I tend to say confirmatory statements such as "I understand," "I follow you," "I hear what you're saying.", in contrast to "Mmhmm","yep","yeah","totally","right", or other phrases which indicate assent.

Protip: Avoid use of phrases which indicate you're about to turn the tables on them until they get a chance to get their full thoughts out, such as "ok" (depending on tone), "yes, but", etc. Ask probing questions which draw out assumptions and fully understand their POV first. Being heard and understood makes it a lot easier to have a conversation on the merits.

If you're in India though, you can use the sideways head bobble. Super effective. (I am not Indian but work in/with many from that culture)
The problem is not abstractions or clean code, it is the lack of experience, lack of time to think and contradicting views of fellow developers in the team. I code for my own projects now, what a joy that is compared to working in a team for company x. Goodbye teams and good luck with your perfect codebases!
> For older browsers there is another trick to trigger the numeric keyboard and include a bit of extra validation for free.

A simpler one that the pattern attribute, but more hacky-er, is using input type="tel", which I’ve also seen used for credit card number inputs.
Null references are not a mistake, they make perfect sense. Letting nullable types be dereferenced directly is the mistake.

Null references are at the core of a great number of sensible datastructures, and they're a natural fit for conventional computers.
Or there's NaN which just results in NaN and doesn't equal itself. No need to crash.
25k? Interesting. I would guess about 2,500 copies based on your Steam review count.

Did you sell a lot more on Switch or something? I really would be surprised if an ASCII game could sell 20k on Switch.
>May be for “millenials” you need to be brave to leave this circle, but I don't getting it.

I don't think anyone is considering themselves brave for decoupling themselves from the Google-sphere. Leaving social media is a far greater step with ramifications, real, imaginary or simply comparatively, that I would commend younger people for being brave should they take the step. It's something that's truly going against the grain.

I think the dearth of these type blog posts is to a) recognize that it's easy to encapsulate much of your digital reliance on Google and its services and therefore b) Real, or imaginary, it's quite difficult to take the step of decoupling from it and finally c) show that it is possible and less burdensome than people currently encapsulated believe it will be.

The authors slant on this is a little different from some others that we've seen on here - Google can shut down your entire online ecosystem with the click of a button should you infringe some arbitrary standards set in T&Cs riddled with legalese, designed for people to not read. A close call opened his eyes, and he made the steps to decouple from Google. I don't think he's looking for some to cry "Oh my, you are so brave!" for doing so.
> Plus you’ll be able to see the Eiffel Tower

A story about Guy de Maupassant always makes me smile. He hated the Eiffel Tower (“I left Paris and even France because in the end, the Eiffel Tower annoyed me too much”) and yet supposedly ate lunch there every day. Why? Because it’s the only place in Paris where you can’t see the Eiffel Tower.

https://www.thevintagenews.com/2016/09/20/priority-french-wr...
Nice job!

For others who want to play with visualizing different search algorithms, this is another cool tool:

https://qiao.github.io/PathFinding.js/visual/
Do You Have to Write Out “2020” on Checks to Avoid Being Scammed?
it wouldn't necessarily. you could just update rust, build firefox and test that. leave the others alone (with older rust).

now if the complaint is solely about rust, not specifically FF, then that's a different story. it might indeed be that FF is the only package using Rust right now?
Tests rarely have bugs, I find, so generally dry isn’t critical. Also, dry is for security (see below)
Generative design tool for urban planning
I think the empirical evidence is against you here, though. If package managers weren't a good way to do things, brew wouldn't exist. Neither would the Mac app store, or whatever the equivalent on Windows is these days.

As a Debian user, I appreciate that the stuff I install had at least gone through some minimal vetting first. And if I have to add a third party repository or download something myself to run, I'm much more likely to view that as the possibly-dangerous action that it is, and try to actively assess the reputation and trustworthiness of what I'm installing.

That's certainly not an average, noon-technical user thing, though. Vetted app stores are there to help average users avoid malware, assuming they're doing their job properly.
Who can blame them. Apart from the very center of Paris (that makes up maybe 10% of the city) with the old town and museums and cafes Paris is a very ugly city.
Transliteration is almost always a mess, rarely yielding good results. If I were him I would just demand the authorities to spell my name as Simon. Or, perhaps, keep it as Semen and make fun of that myself. I could even sue someone who would ban me for this.
It's been possible for multiple people to edit an Excel file simultaneously for a long time. Since 2017 (at least) you can use OneDrive as the file location, so you get all those syncing and sharing benefits you mentioned. The newer Click-to-Run installer takes about 2 minutes to get the app to a usable state, and if that's just too long, there's always https://office.live.com/start/Excel.aspx
Doesn't Rust use static linking between crates as a rule, precisely because dynamic linking would break given reliance on anything but a pure C-like ABI? (BTW, the cbindgen tool mentioned in the linked article is meant to address precisely that - provide a clean interface to a Rust crate that won't break with internal ABI changes.)
The point of dry is to avoid having to redo code review and security analysis which can be quite lengthy and onerous. Fixing Bugs in many places is another thing, but not the main thing.
Refactoring duplicated code is a trade off: on the one hand you create abstraction and centralizing code logic at the cost of, first, the overhead of learning that abstraction, and second, by increasing coupling between functions. I've personally found that the coupling is by far the most important factor to consider. If A depends on B, and C is found in both A and B, then you should factor out C. If A and B share C because they are adjacent, without being fundamentally intertwined, then duplicate C, but consider creating a library or module that makes it easy to talk about things that are similar to that duplicated code, C. (I tend to think about modules/libraries as little, independent DSLs)
It's also about memory consumption.
A high schooler keeps scooping news outlets’ Iowa polls
Never talk to police. They are not your friends.
I recently switched to Fastmail and I'm very happy. The web and mobile apps are blazing fast and simple. My favorite feature is being able to add unlimited aliases which sends/forwards to whatever address I choose. This has enabled granular control over my inbox as I have receipts@mydomain, bills@mydomain, finance@mydomain, etc. If I want to try some service, I might create an alias. If they end up spamming too much, I can simply delete the alias or apply other rules.
I love that show. I picked it up again a couple weeks ago after trailing off during Season 2 because of work.

Agree with all your points, and I'll make one more:

The way that they blend the "gesture" interfaces (the "iPhone" device, the map and orbit planner, the wall screens) with tactile interfaces (physical keyboards at critical positions on the spacecraft, like weapons and burn control) signal they put some deep thought into it. Gesture and touch-screen stuff is fine, in very specific instances. You will need a tactile surface to touch in many of the kind of (future) environments that the show depicts.
So this is kind of like the DLL hell Windows had?
I feel like the way to do this would be to have (1) digital repro format & (2) auto-exec of submitted issues to verify.

Then have the workflow look more like (1) anon q public submits repro file & issue description, (2) auto-test system runs and validates repro file, (3) issue auto-logged, (4) issue cannot be manually unlogged without fix (if upstream, move to side filter, pending upstream fix)

The human triage stage usually seems the most adversarial. So having an automated system take it to "Yup, this is a bug" would be a good start.