skysight-inc/HackerNews huggingface dataset:
I think this rant is going against the irrational outcomes of a few things

1. People tend to put excessive hope in silver bullets, quick fixes, and the easy path. "Discipline" is generally shied away from.

2. It's an attempt to save the more expensive thing (engineer time) for the cheaper thing (RAM) especially in the face of rapidly improving hardware (which may no longer be true).

3. As engineers become expensive, people who have little interest in the subject become sufficiently motivated to hit the minimum bar, bringing down the average talent/quality of the pool. I am daily shocked by the number of engineers that do not understand the differences between implementations, and how "good enough" for a single scenario is not "good enough" for a complex and unpredictable future. Your 1 month implementation may be "faster" on paper, but if we consider the implementation time until yours and mine have acceptable robustness under duress, acceptable bug counts, predictable outcomes in unpredictable scenarios then my 6 month implementation will beat your "requires rewrite" (quarterly) by years... But never mind that, the engineer with the crap impl will "save" the company $100K a month in opex when he cuts the inefficiency in half and be promoted to architect. Meanwhile the engineer that does an efficient impl, maybe slightly over schedule will languish because there isn't even a 10% gain to be had, or the thing runs so stably the project is entirely forgotten about for years (because it just works) ...

So yeah, Electron is what we get when we pursue logical fallacies with little to no accountability for the true outcomes, and no rewards for excellence and subject mastery. Yup I'm a dinosaur too.

Anyways, I'm ranting now too...
> I'm irritated by the implication that it's the user's responsibility to do this

I don't think it's so irritating. When you set up your phone you are prompted to allow iMessage to use the number. If you allow it you'll have to remove it again after you decide to not use it again. Just like you have to cancel a subscription if you don't want to use it any more.
What do you mean by "Apple only supporting iMessage"? If I want WhatsApp I use that app, it sends notifications, it can even ring my device for a call. Same with FB/Signal/Telegram/etc.

The view that Apple is forced to support other protocols or networks "just because" is pure idealism.

The history of technology and business is a "maze of twisty little passages, all alike" for longer than we admit. Interoperability relies on government/intergovernmental mandating of standards - if you leave it to industry you get patent encumbered formats (see H.265).
All Apple has to do is wait this out as the social ostracizing is just a convenient side effect of their scarlet lettering. The color coding was made to inform users that SMS fallback was being used if green, which went on to mean "unencrypted". Monopolies are tolerated if no anti-competitive practices are employed, here, the competitor shot itself in the foot 13 times and asked Apple "why did you do this".
I don’t consider that a reasonable risk. And even if it was, then I don’t care for repos I explicitly clone without using encryption.

There’s a large set of “I don’t care” style projects where I’m just looking to grab a copy. So even if my ISP (or some nefarious jerk on the same WiFi) could MITM, I don’t care. Plus, I’m not aware of any attacks like this because of the whole git checksum thing it’s harder than injecting into http traffic.

For stuff I care about, I log in.
Discontinued Long Term Support for AngularJS
What I want to know is, if the threat was deemed to be great enough to have airplanes land, why wasn't the public notified to seek shelter?
To add some fluff to this:

At one point twitter seemed to want to be a relatively general protocol, where users could build their own UI, use 3rd party apps and maybe even interoperate or extend with other social networks & such.

Pg/yc even wrote about it, inviting startups to start writing apps for this exciting new protocol. The early app ecosystem was pretty slimy, with a lot of spam-ish clients for promoting snake oil. More importantly, it became clear that controlling the UI means control over users: the data, rights, often and the ability to decide what goes into people's feed. That's where the (financial) value is, and they're not going to give that up.

TBL's ideas were naive perhaps, but he did have his thumb in the right place. Something like semantic web was necessary, in order to avoid the centralisation that did end up happening.

RSS, via podcasting did catch on. Today it's one of the only "free" media forms. There's no company moderating podcasts like twitter, FB, youtube, etc.
Hangouts was killed; I was actively forced to migrate my SMS stuff back to Google Voice, and Google Duo is what replaced it for video chat.

The 'internet chat' they introduced a different service called 'Chat' which runs in some consumer version of Google Workspaces.

I also really hate XML based chat, but the OG standard failed because the federated clients had a poor required minimum standard for interoperability and other stacks E.G. Microsoft's whatever version of it ... I actually forget offhand but it was something anti-competitive that also broke how useful it was outside of their particular implementation.
Google really needs to get its nearest competitor under control before they go after others. But Google can't get itself under control. Too busy shooting its own products before they can run, walk or even crawl.

Bikeshedding at scale. This is what it looks like. I'm surprised that their home automation systems don't have some incompatible chat platform embedded in them.
"The Rise and Fall of Commercial Smalltalk" discussions provide a fuller picture:

https://news.ycombinator.com/item?id=29223880

> … storing source code inside a memory image didn’t help with interoperability…

"Interoperability" covers a lot of things, was there something particular you had in mind?
Sure you can. That is why I am in favor of limiting the scope of these organizations. Individual employees can, and do, bend and selectively apply the rules. That doesn't necessarily make democratic republics intractable - the continued existence of the US proves that.
Ultimately I kind of agree with the sentiment but the sensationalism here is cringe. Also, some new tools and languages are indeed worthy improvements. It's worth calling out the ones that aren't; lashing out at all new technology as a whole is not how you should come at this issue.
North of England was what I had in mind. I guess "soda pop" (US) and "fizzy pop" (UK) might have a common root.
> There are countless other methods for communicating by text on all of these devices

And only one of them (the one made by the platform vendor) can degrade to using the sms service that the hardware is capable of and I pay my carrier for.
I'm not a fan of counting medicare or social security in "all taxes collected".

They're collected separately (and they're also really badly designed, but whatever).

So I rather us look at the amount we're spending on stuff that doesn't get a different line item on our paychecks.
This is 95% criticism about C++20 ranges (specifically the ranges v3 implementation), but spun as being about some more general trend. I think some of the criticism of ranges is fair - compile times do matter and non-optimized performance can also matter.

Stuff like `iota` being obscure is less convincing. It wasn't invented here and it is anyway something you learn once and then it's part of your vocabulary.
I enjoyed the speculative bias there as its prompting me to pick up the sqlite bundle thats been sitting in my downloads while i use post-gres-like-the-rest
Depending on something doesn’t mean crazy. I depend on lots of OSS projects (and windows), but I have a management system where I control what gets updated and when.
There is a wiki extension to embed RDF data: https://www.mediawiki.org/wiki/Extension:LinkedWiki

There is a WP plugin to expose some basic data: https://wordpress.org/plugins/wp-linked-data/ and a Swedish startup Metasolutions has Wordpress plugins for embedding any kind of RDF information: https://docs.entryscape.com/en/blocks/
I think the idea is that once you know what is going on you can opt out, so that you can put fixing it on your next sprint instead of having to drop everything and fix it right now so you don't lose 24 hours of productivity.
Git.io no longer accepts new URLs
This description matches American prisons pretty well. Of course US puts many more people there.
These days I look up individual features, and use the date-relative view, to assess how long it's been available. Normally I'll start porting features once they're solid across the main browser set, but with a polyfill or some alternative based on feature detection.

I held off on delivering ES6 native until 2017-2018, and used mainly Bable or sometimes hand written polys up to that point if I wanted to use features from cutting edge. There's some influence from your user-agent analytics as well to determine if there is a meaningful regression to leave people behind.

5 years is just the rough grasp, sometimes the new features are worth integrating sooner if they provide actual functional improvements for users. Generally, syntactic sugar is given less precedence especially when it would negatively impact usability of the product. Saving a few hours for development is far less valuable than saving even a few hundreds of users hours of frustration.
If Mike Pence had been complicit, they wouldn't have needed the rioters. I agree that "it" was serious, but the "it" was Trump's attempt to not certify the results of the election, not so much the protest/demonstration/riot/incursion into the Capitol.

Mike Pence did what he was supposed to, under severe pressure to do otherwise.
The country (especially the left) owes him a huge debt of gratitude.
> I don’t see how you’re not suggesting yet another competing platform

I'm not suggesting another competing platform. I'm suggesting an already-widely-deployed platform (RCS) that is standardized, has been around since 2008 or so (older than iMessage!), and is the actual real elevation of SMS, not an Apple-proprietary protocol.

> If iMessage was cross platform

It's not, and that's the problem! Making it cross-platform would at least partially solve the problem, though it does mean Yet Another Messaging App I have to install.

> If you want secure cross platform messaging, use any of the other platforms built around that feature.

That's a huge pain in the ass. Not all of my friends have Signal, and I'm tired of evangelizing. Not all of my friends have WhatsApp, and I'm not interested in evangelizing a Facebook property. I don't use Telegram, and very few of my friends do, and I'm also wary of evangelizing a messenger that is not secure by default, and that has what is IMO a sketchy, secretive history around its cryptography.

Looking through my Messages history, there are 27 people I communicated with over unencrypted SMS/MMS over the past month. Only one of those people has Signal (not sure why they SMS'd me, but that just further illustrates the problem of how it's difficult to remember to contact people using the "correct" means), and maybe 6 or 8 of them have WhatsApp (for whatever reason, they/I don't really use WhatsApp often).

Why is this so hard? Apple! If Apple supported RCS (with the E2EE extension), literally every single one of those 27 conversations would have been encrypted, without me (or, critically, the other party, whom I have no control over) having to do anything special. As much as I love blaming Google for many things, they cannot solve this, because iMessage is a closed protocol that they are not permitted to implement, and the messenger app that is in the default install (the iMessage-supporting Messages app on iOS, and the RCS-supporting Messages app on Android) has a huge easy-adoption advantage that third-party messengers will never be able to match.

You can argue a bunch of "shoulds" here, but I'm talking about what the reality actually is.
Just because they don’t have a majority share of global sales doesn’t make them a “minority player”. That’s not really what that term means.
The term “minority player” means they have less influence/importance than the “major players”.

Though, to be fair I can see how that could be confusing (because English).
They are #2 globally, behind Samsung. 15.2% of the global smartphone market to Samsung's 20.8%. They are #1 in the US, 47% to Samsung's 34%. That is a dominant position. Apple would be wise to avoid the appearance of abusing that position and inviting regulatory oversight.
NAD & Chromecast? My NAD amplifier is about 22 years old. It doesn't know anything about networking, streaming or chrome. It's an amplifier.
I agree with your argument. The comment about blogs taking long to load leads me to believe most of these complaints are really only applicable to small scale projects. The massive stacks used for web development now are targeted at organizations that can scale into the hundreds or thousands of web developers with varying skills. In turn, when doing small scale work, most newer developers copy the massive enterprise stack, pay the price for the possibility of scaling (both requestwise and developerwise) without every really needing to.
Electron is literally the only reason Linux desktop is somewhat of a viable option right now lol
I always want people to patent TERRIBLE ideas, to prevent game companies from implementing them.
That's the key. In software if you want good estimates, get developers to build the same app again and again, throwing away the source code each time.
As a Canadian living in the US, here is my experience:

Advantages

- Higher Salaries (as a SWE, but similar for friends in other high skill professions)
- Faster, more accessible healthcare
- Easier access to COVID vaccines/boosters
- Access to more products/services
- Amazon has everything
- Better credit card perks

Disadvantages

- Actually using healthcare is expensive
- Losing my job is insanely scary (losing healthcare)
- Way more advertisements (billboards, credit card offers, drug ads)
- Banking is way more fragmented
- The wealth gap is visibly wider (rich areas are slightly nicer, poor areas are far worse)
That’s why it’s a design patent, which is completely different concept from an invention patent.

For one, it lasts forever.
Airlines aren't exactly known for fabulous margins. I get your point, and I never feel bad for a corporation, but I think airlines are probably one of the few sectors with a hypercompetitive market, tons of options, and pretty low margins. they have basically 0 monopoly, so they compete very harshly on prices and services. Also, I'm not sure who the insanely rich backers would be considering airlines usually aren't exactly family empires and have pretty mediocre investment returns
It’s not necessarily the same, but it’s a good co-signal. And definitely useful for refuting emotional, data less calls that the sky is falling.

I’ll take a decade of success as a sign of sustainability over a package maintainer losing their shit as a sign of h sustainability.
What sort of tools read .env files/what do I need to know to comfortably set and read environment variables in PowerShell or Bash? Do you just keep the token there in plain text in the .env file?

If you have multiple work stations, do you have a method to keep your secrets synched?

Sorry about all the questions! I appreciate any insight you might have on this though.
Please provide a better analogy. I don’t see what using electricity has to do with poisoning water.
Exploration will decline, and drilling, as expectation of demand falls. We can expect substantial fluctuations as numerous structural boundaries are crossed. Coal demand is collapsing, but price is not, because there is no cheaper way to mine coal.

At some level of consumption the cheapest existing wells will suffice. But the owners of those wells have got used to spending a great deal more than the natural price for that oil. Meanwhile, people with more expensive wells have debt payments, and have to sell at whatever the market offers.

So, it is more complicated than Econ 101, and will stay that way.
>Also, keep in mind that no matter how much you invest, studying at an American university opens the door to working in America and getting a western passport, something more and more Chinese are desperately trying to do.

I'd heard the opposite; that in recent years fewer Chinese studying in the US are staying, and that more who had stayed were returning to China, because of greater opportunities.
Yeah but something tells me that someone who's in favor of "redistributive economics" isn't the type of person who thinks "Both took the job with an awareness of whether the job was tipped or not" and therefore it doesn't matter what they earn.
>Meanwhile, the shitty tech is winning. According to this author, bad code and bad tools and bad frameworks are reigning supreme over real engineering. Why?

Because in the time that OP spends tracking down segfaults and getting a dozen native libraries to compile for his native app, the JS dev has already finished XYZ feature. And because the environment is so high level, he can use the extra brain capacity for things like UX, business logic, and accessibility (things people actually care about) rather than meaningless implementation details.

This stuff won out for a reason. HTML/CSS/JS is literally a 10x improvement in iteration speed versus native.
> Is that the work of heroes or the misguided?

Precisely both, since no one agrees. At least money can be used as a fitness function sometimes, with games and not with enterprise. The idea is that if D were that much better people would make more money by choosing it over Java.
You don't understand my argument, which has nothing to do with whether we should charge for street parking (we should). There's not much point in us continuing here.
> This is why I'm surprised I've not yet seen a VHDL/Verilog compiler for minecraft redstone.

https://github.com/itsFrank/MinecraftHDL

https://devpost.com/software/mcverilog
what if it is stolen/broken and you don't want to buy an iphone but an android ?
This comment sheds a little bit of insight here: https://news.ycombinator.com/item?id=29895421. The original article chose to always go "clockwise" around the color wheel, picking up lots of different colors and giving the appearance of a rainbow, instead of taking the shorter, more naturalistic route of blending through teal & green.
Yep. When I saw the tired "Electron = bad" rant I immediately went to look for a tab entitled "Projects" to see if the author had created a native desktop app with "value"[1] equal to or greater than what a good Electron app provides (Slack, Spotify, Discord, VS Code). But lo and behold, no such tab.

[1]: [Electron apps] constantly crash and has no value over a native desktop application what so ever
You want to look as "boring and regular app" as possible, to avoid detection based on heuristics. So that means using no "malware techniques" like DLL injection, process scanning, fancy persistence, ...
Or your email client would open and execute every file attached and it would do so with root permissions.
Dumping Firmware with a 555
The time to stop discussing the broken patent system is when it is no longer broken. That time is not now.
Apple to allow third-party app payment options in South Korea
While I like the annotations, I have to say they make it difficult to make out the original equation. It parses and highlights variables and gets in the way of seeing a cohesive whole equation.

I think an annotated version would be good as a supplement.
Although "Mad Men" isn't a documentary it does show how easy it was to board a plane in the early 60's. It agrees with what the adults said was the reason hijacking was so easy then.
I feel this. On the subject of Boost Geometry I cut multiple minutes out of our build times by removing all instances of "#include <boost/geometry/geometry.hpp>". I hate that the example code seems to encourage this - https://www.boost.org/doc/libs/1_64_0/libs/geometry/doc/html... as it adds a few seconds to the compilation time for each TU that does this (which can be most of them if you have it in another header).
This post came 3months before phiresky, and should get credit for being first to making it practical:
https://news.ycombinator.com/item?id=25842999
That is true.

However, market forces guarantee that the difficulty will go up to the point where it's infeasible to add more hashrate, e.g. because it becomes uneconomical or there's simply no more hardware available. PoW workchains must work at maximum inefficiency. (This bears out in the data, too, I think. BTC had its highest hashrate at the beginning of this month, when energy price were at an all-time high and BTC was at the lowest over 12 months)
Domain-Specific Types for Primitives
I definitely agree with the diminishing returns of remaining in Canada as you become wealthier.

I’m making the move this year. As a single income household there are a lot of tax advantages in the US compared to Canada.
> Except Apple is highjacking your phone number and won't let it go without a fight

You know you can just disable iMessage and then the service is not used.
Citadel Securities taking outside investment from SV firms Sequoia, Paradigm
Effectively, this is a pretty cool way to get an OSS version of something like https://www.snowflake.com/guides/public-data. Also something like a lighter version of https://datasette.io/.

The thing it's kinda missing for me is the ability to compose multiple SQLite databases, possibly provided by different domains.

It'd be nice to join together different public datasets. In a weird personal example, if Strava exposed SQLite, I'd love to do a join to weather.com and see when the last time I biked in the rain was.

It'd be cool if one half of some table was at foo.com and I could add a few rows to it on my bar.com domain, and then the combined dataset was queryable as a single unit.
Why I've updated my about page
GitHub public projects are free of charge, for the benefit of the community. It's good for the community that massively breaking changes that break every single consumer, are quickly fixed, even if the author wants to break the software. The author is free to publish their breaking changes elsewhere.
By "reasonable" I mean "can be reasoned about" - not "is it the best way".

http://the-whiteboard.github.io/coding/debugging/2016/04/07/...

While that speaks of code - the key in there is the ability to look at it and figure out how it works and how to change it.

With Log4j, we had to select one of those approaches, rebuild, and redeploy. In the Java community, repeatable builds are valued - the "I build the jar today" should have the same result tomorrow as the default.

It is possible to change the way maven specifies its versions to do ranges, just most people don't do that. I don't want my oracle ojdbc jar to suddenly jump to a different version that doesn't work with the backend I'm running.

---

https://www.sonatype.com/resources/log4j-vulnerability-resou...

If you look at the "downloads per hour" you'll see that about half the people using it downloaded it and continued to update their code as new releases came out.

It is concerning that 41% of the builds out there are still specifying a vulnerable version.
Bad analogy. This is not a case of competing products. It’s a platform vendor using their position to push their service over competing services. It’s like if fararri sold a car that could run self-driving software from various vendors, but only allowed their in-house self-driving software to make left turns. Sorry Ford Pinto Self Driving software - no left turns! Yes the hardware is capable of it… no you can’t do it only we can.
40 Years of Quantum Computing