skysight-inc/HackerNews huggingface dataset:
Aaand now you've gone on to dispute Moore's Law, as if the specificity of the "two years" part was at all critical or even important to our conversation.

Also, that link you provided seriously undercuts your own argument, you do realize that right? It very clearly shows how over 90%+ of computers have 4 GB or more of memory installed, which is plenty to run multiple Electron apps.
I am more and more on your side. If this function was a builtin, how many reader will check its implementation?
Fascinating! I wonder if multiplication/division is just a combination of these neurons or again some other.
The Hurd is actually older than Linux now at a ripe age of 32, although I think it was Mendel Rosenblaum that said "hypervisors/machine monitors were microkernels done right".

https://www.usenix.org/legacy/events/hotos05/final_papers/fu...
Jami: Synchronizing Conversation History with Swarm
> to kill every last Japanese person, military or not

This is a war crime.
You can delete the data that google currently has and reset your advertising id.
> It's like all of these password manager tools were created by people who've never seen nor used these existing solutions.

Maybe, but it sounds like your comment was written from a place where you've never had to actually implement one of those existing solutions.

Kerberos is great. It's also a holy terror to implement properly, especially cross-platform, and especially if you need to federate identity.

I've been down that path. While there are trade-offs with any decision, I wholly understand why so many organizations are going to solutions like Okta/Auth0 + Duo + password managers vs the "tried and true" methods of a directory server + Kerberos + SAML federation through Shibboleth

SCIM combined with modern cloud SSO makes life much easier than trying to support Kerberos.
I just posted this in the commentary about safety of nuclear power in America:

"Of course there's a worst one, there has to be. Well Hanford didn't principally produce energy, so much as just plutonium, so really its mission was weapon production. So now we're changing the subject a bit, no longer is it about electricity, but defense.

So we can address that immediately: without the Hanford site, Japan would not have surrendered without an invasion of the home islands. Maybe not even then. It was the "new and cruel bomb," as the Emperor of Japan described it while citing it as the reason for surrender in his speech. That "new and cruel" bomb meant an alternative to reenacting the Battle of Iwo Jima (which I would describe as "fucked up" for both sides without question) a thousand times. Battles to the last cartridge. Forgetting completely about the lives of Allied and Axis soldiers, you realize the death toll that would have on the civilians of Japan? They were on the hook for all kinds of atrocities all over Asia and the Pacific, in the context of total war they pissed off the rest of the world way too hard for the Allies to declare a truce. Just in Korea alone, the stories are just...let's not talk about that, let's stick to what is fucked up within nuclear science.

Japanese were subscribed to the idea that their genocide was preferable to surrender. So that's why the bomb, and by extension the Hanford site, were so important. In practice the nukes in Japan explosives second, fireworks first. Napalm was a much better explosive for the money, in terms of the destruction it could produce. The really bad bombings in WWII were in Tokyo and Dresden, a hundred thousand dead per bombing, a new climactic event called a "Firestorm," terrible burns, pavement getting goopy, high winds--I claim those bombings were worse. But they weren't as flamboyant as a star."

https://news.ycombinator.com/item?id=30362668
Where I live in Spain it was mandatory again until last Friday and a lot of people still do..
The official Postdam Declaration (allied surrender terms) didn't mention imperial sovereignty one way or the other, but it appears the Emperor considered it to have been agreed upon prior to the "unconditional" surrender

Some more color, from Wikipedia:

"The Japanese cabinet considered the Allied response, and Suzuki argued that they must reject it and insist on an explicit guarantee for the imperial system. Anami returned to his position that there be no occupation of Japan. Afterward, Tōgō told Suzuki that there was no hope of getting better terms, and Kido conveyed the Emperor's will that Japan surrender. [...]

That day, Hirohito informed the imperial family of his decision to surrender. One of his uncles, Prince Asaka, then asked whether the war would be continued if the kokutai (imperial sovereignty) could not be preserved. The Emperor simply replied "of course.""
> I don't see anything wrong with teaching those basic concepts from a mathematical perspective.

One thing that often goes "wrong" with this is that the mathematics of frequency ratios is a huge barrier that's most often irrelevant to actual music making. If you literally know nothing about music, there's a good case for just letting the tuners deal with it for the time being, and starting from the old Do, Re, Mi etc. that teaches you both solfège (sight reading/aural skills) and the musical syntax of scale degrees. Then sing a whole lot of music in (movable do; fixed do is pointless except for specialists) solfège and try to make up simple embellishments and variations on what you sing. There's a "programmer's favorite" way of learning these too (these are called diminutions) based on the scale-degree leap that you're traversing, hypothetical elementary operations of musical syntax and whatnot; but good musical intuition will always be helpful. Guess what, now you're well on your way to improvising simple music at the keyboard, and later on you can even get started on learning counterpoint without being lost in all the details. Because, unlike actual college students who are forced to take a counterpoint class as part of studying bookish "music theory", you'll have the fundamentals down pat.
Gaining miles slowly is excellent advice, probably the most important advice for new runners. It's a mistake I certainly made more than once both barefoot and not, though thankfully it never resulted in anything as severe as shin splints or metatarsal fractures.

These days I'm generally pretty good about listening carefully to my body and respecting my limits -- I'll stop the run or ride if something starts to feel off. It's an approach that's served reasonably well for more than a decade. Though I can afford to take things slowly because my long-term goal isn't to to set speed records but to keep running well into old(er) age.
I think the majority of it is down to the pre-SaaS customers of the product. 1Password used to have a life time license and would work without any need for 1Password servers. You could backup your vaults anyway you wanted and the various clients would work with a variety of methods for syncing etc.

A lot of long term 1Password users bought this and still use it, but the company no longer really do much to support it having pivoted to completely focus on their subscription offering. Many of their long time customers, many of which are HN users, feel they're getting shafted by the lack of updates etc to those older offerings. From what I understand a lot of the older clients and plugins that worked with the local versions don't get updated anymore. However, I'm only a customer of their subscription offering so someone else might be able to elaborate more.
Unity, Unreal, and other modern 3D engines let a solo developer create something that looks nearly AAA if they buy decent assets. The problem is that turning a pretty walking simulator into a game with good mechanics, interaction, sound, consistent style, and a fun factor (not to mention story and characters) is always going to be hard, unless you’re able to ask GPT5 to generate all of that for you from a few sentences. If you have a pretty physics/walking simulator, but very shallow mechanics etc, it feels hollow. If I had to guess, I’d say that an equivalent amount of development on a 2D pixel art game will give players less of that hollowed-out feeling. The more graphical detail you provide, the less is left to the imagination, and therefore the implicit expectation of detail goes way up.
The nice thing about using an event system is that you can just record all events. This allows you to record gameplay directly. This can be used as a demo, scripted scenes, and especially for debugging! Encountering a bug during playing? The recording can be used to reproduce the bug, as it will be a "pixel perfect" playback. Code until it is gone. Debugging is suddenly way easier, as you can just check the events wireshark/tcpdump style, and see what went wrong.

Even more, in networked games it can be used to roll-back actions you did (e.g. because someone with a 100ms ping shot you 50ms before launching a rocket, to roll-back rocket-launching animation). Or in the simulations of the behaviour of the other players (peeking around the wall).
> I definitely understand the aversion to trusting 1password's cloud service, but it's worth noting that their security model is such that it requires minimal/zero trust of the server.

It just requires absolute blind trust on their client apps...

> Your vault is only ever decrypted on the client side

Which is a closed source blob, so, again, requires absolute blind trust.
Whether or not he should have been let out at all is completely independent of the cash bail system, unless you think that the decision of whether or not to release him should be contingent on his financial situation.
I have used 1Password since way before the cloud version became the default. I loved the product... and I still do! I moved to the cloud version and the experience has been really slick.

I actually think the product is well thought-out and designed. There are some website where it refuses to work, but these are in the minority, and I blame the websites for breaking 1Password, not 1Password.

Also "a nightmare" -> this feels like an unnecessary hyperbole
just tell them you're old and they'll instantly go away, never to return.
But it is not a builtin. Someone else is going to have to maintain this one day.

> insert quote about writing your code as if the person who will have to maintain it next is a violent psychopath who knows where you live
You can have reliable power or cheap power.

The problem with current regulation is that power is treated like a fungible commodity when it is not.

Base load should be priced separately from peak and intermittent generation.
Surely an attacker can just proxy this? Seems like security theatre to me.
This is an extremely bitter outlook on life. When coworkers land jobs at places I've bombed interviews at, I'm genuinely happy for them!
I use it for sms and phone calling through jmp.chat. Though I'm afraid that carriers are going to sandbag it if it gets popular.
Isn't storing passwords island 2fa in the same place a bad idea?
> It's a huge ugly monster with dozens of keywords (buzzwords?). You spend 6 months passing an AWS exam, and all you have learnt is how AWS works.

This was actually the comment that stuck out most to me. Because it's an abstraction of the specialization that's going on in the industry that worries me. Sure, you can learn general computing skills as a side effect of pursuing this efforts, but increasingly, we are learning how to drive tools, rather than solve problems. The effort to grow proficient with increasingly complex tools and frameworks is greater now than the effort to grow proficient in a particular language (even some of the more complex ones).
It's a question of supply and demand.

In areas with high supply or low demand, the price of housing approaches the cost of construction.

In places with punitive zoning rules that forbid new construction, limiting supply, and have high demand (I'm looking at you, San Francisco) the price of housing dramatically exceeds the cost of construction.
Almost nothing, especially with the cheap materials used in current modern construction (unless requiring some hurricane code; ex. South Florida). It's all due to zoning limitations, and homeowners voting in their own interests to keep the supply down, and values to rise.
Yes, of course, does breaking the rules not lead to better music automatically.
But strictly adhering to the cultural/mathematical rules seems to lead to mediocre results.
For sure, there's a bit of that. You would still agree w/ the point I'm making?
My workflow tends to be:

- Build it in blueprints for rapid iteration

- Port it to C++ for refactoring and long-term code quality

I was bullish on the node based programming, but over time I've liked it less and less.

I've been a software engineer for 10+ years so I am very comfortable in the IDE and coding workflow.

But yeah, discoverability in blueprints is out of this world. And the C++ classes use the same functions as the blueprint classes. Once you figure out how to find the C++ the blueprint is calling into, it becomes very productive.
To be fair, the Pinephone store very clearly states that this is a beta device intended for experience linux developers/early adopters only. It’s not meant to be a daily driver yet.
History is back around to repeating itself. I'm an avid Linux user (and even a developer who uses GTK pretty regularly), but the recent developments surrounding GNOME, Flatpak and their related libraries has not made me optimistic for the future of Linux applications.

GTK4 is really bad. It launched with horrible text rendering issues (still unfixed, 10+ months later), broke compatibility with a number of basic features, and then had those features replaced by the GNOME middleware known as libadwaita. libadwaita is in a "functional" release state, but still lacks support for custom stylesheets, basic desktop integration on non-GNOME desktops and has it's own litany of bugs that accompany it. Fair enough for brand-new software, but the state of GTK4 is unacceptable and borderline impossible to use on a daily basis. If you're a developer, things only get worse. Gone are the days of fast app development with gtk::Builder workflows, and now Glade has been thrown by the wayside with no replacement. Talk about a second-class developer experience. And then there's the strange omissions that the GNOME team insists on; some issues are marked as WONTFIX since they can be mitigated with Flatpak. Some features (like appindicators) have been ignored completely because they don't align with the GNOME desktop's vision. The general demeanor of the team has been my-way-or-the-highway, so making suggestions mostly gets you labelled as a troll in their gitlab and sees you forcibly removed if you don't give up and assimilate into their opinion.

Flatpak itself is becoming the new Wayland. With more than 600 open issues on Github and outstanding issues like random data deletion, portal malfunctioning, compositor glitches, security holes and more, it's less like the "one package manager to rule them all" and more like "snap but it doesn't work". It's slow, doubles the dependencies that you store on your system (!!!) and doesn't integrate with your desktop unless you go out of your way to install questionable third party hacks that forward your native stylesheet and XDG options. I'd honestly rather use AppImage if given the option.

The future of app development on Linux is bleaker than ever. Fragmentation is at an all-time-high, and the technology that was supposed to fix it only fanned the flames into an unsalvageable dumpster fire. If you are a Linux developer planning on shipping an app, please stay on GTK2/3 for the sake of your users. I outright refuse to run GTK4, libadwaita or Flatpak on any of my systems. Nothing I've seen recently changes my opinion on that.

Dead dove, do not eat.
The camera is so bad that it's even a shame that they bothered adding it. The additional cost for the hardware clearly wasn't worth it.
I have this with wordle. I mean I still don't know what a caulk is.

(it's to the east)
> The Chrome sandbox efforts have been going on for 3-4 years with no progress.

There has been progress: many APIs have been implemented in Chrome, with several origin trials for testing them and iterating. Ex: FLoC started an origin trial, people raised issues, Chrome proposed a replacement (Topics) which looks like it will be in origin trials soon (https://privacysandbox.com/open-web/#the-privacy-sandbox-tim...).

(Disclosure: I work on ads at Google, speaking only for myself)
So they didn’t suffer the same adverse effects.
I wonder why they picker $HOME instead of the obvious choice like $XDG_RUNTIME_DIR.

It's not like I'll ever need to manually interact with the socket, so keeping it out of the way would seem logical.
> Qt clearly deserves the credit for having a WASM runtime that gets us a working GUI toolkit.

You're welcome. :)
What version of Qt did you use for this demo?
Also, for local system file access dialog on Qt wasm, you can use
https://doc.qt.io/qt-6/qfiledialog.html#getOpenFileContent
Interestingly enough, that view is being challenged right now. (I have a book on my bookshelf waiting for my intention).

Taking Hitler's second book more at it's words - its more that Hitler desperately wanted to get Japan into the War to keep America out of the war long enough to knock Soviet Russia out. He committed to declaring war on America if Japan did (prior to 12/1) to try and get Japan to take the brunt of the damage up front front.

Hitler bet that like in 1918, it would simply take a long time for the USA to build up it's armament. But it's also clear that Hitler viewed the United States - as agents of World Jewry - and it's continent of resources as the ultimate opponent for a unified germanic Europe.

(The best source off the top of my head for this PoV is Adam Tooze's Wages of Destruction).
Aha! That was a bonehead miss on my part. Very nice, and very slick interface. :)
The impression I have gotten from articles which look at the Analytical Engine more critically is that Babbage had the habit of trying to upsell his investors into a more complex, more risky, more academically interesting device without completing the last one. The Difference Engine actually was completed eventually and ordered by the British government, in a more pragmatic form: https://en.wikipedia.org/wiki/Difference_engine#Scheutzian_c...

That said I do agree with what was said in the thread. There was a lot of accidental complexity in early numeric computers. I feel a true programmable computer could not have come about without the development and refinement of symbolic logic that took place in the 20th century.
Seconded. I also found my skills transferred easily outside of games themselves.
I used to do this exact thing as a job, and it's crazy how little US brokers do to protect their APIs (at least back when I was doing it around 2015), given the security implications. I'm not even a hacker and I was able to reverse engineer 90% of the US brokerages without a problem.

Compare that to Singapore. I spent about an hour toying with the Lim & Tan API before our account got shut down. Apparently the fucking CTO was woken up in the middle of the night by all the alarm bells I set off lol.

edit: when I say "without a problem", I mean that in relative terms. We got plenty of strongly-worded letters asking us to stop, and they played whack-a-mole with our instances. But we never faced a serious challenge to what we were doing.
> More specifically, the United States didn't go to war at all against Germany until Hitler declared war on the United States.

You can say the same about Germany. They didn't go to war against France and England until they declared war on Germany.
LinkedIn is a job board.
It's actually a very good job board, I use it tons to search for jobs or candidates.

I don't understand why people try to treat it like a social network, just don't and it works like a charm.
> There's nothing left, privacy is a myth from a different era of the internet.

GNU/Linux phones (Librem 5 and Pinephone) are here to help.
I think one of the problems is "what is google" and "what is phoning home". So many of these services make simple requests that wouldn't be considered "phoning home" but absolutely fall into that category. Additionally, the number of google products and the number of calls being made is vast.
And Google really only has itself to blame for that, TBQH. They have had how many mediocre chat apps that they could have turned into Discord with a baked in user base over the past 15 years?
Yahoo used to do this, called Yahoo! Sign-In Seal. Not sure if they still do it.
> If the private key is on your Yubikey, you're already good.

This is the way.
I'm just getting into game dev, though starting with the tic 80 [0]. I've found it kind of funny how, like, matter-of-fact it is. In my mind there was always some magic algorithm going on and I guess there arguably is but it more like, "check the x and y coords plus the character's height and width and do those coords touch a coord on the map that is considered solid and if so, set the player's velocity to 0." It's like, "Oh ya, duh. Damn, I was hoping it was just magic."

In the spirit of this article, I was going hard at it for several days but have not worked on it since last week.

[0] https://tic80.com/
My co-founder and I almost made the exact same transition you mentioned. Frustration with Plaid and MX made us wonder if we should just built the integrations ourselves and make that our company. We'd be interested in staying in touch and potentially partnering
> some of the pitches in the harmonic series are approximated by the notes of the chromatic scale

is not the same thing as

> the chromatic scale is derived from the harmonic series

which is what the OP article claims.

You can find the chromatic scale in the harmonic series, yeah, if you ignore the majority of the notes in the harmonic series.

To find the chromatic scale in the harmonic series, you need to take the 2nd, 3rd, 4th, 5th, 9th, 15th, and 44th harmonics, and ignore of the rest. That's not a mathematically justified derivation, that's a post-hoc rationalization built on coincidence alone.
Ah, you're right about the sticker. I didn't zoom in on it when I first watched the video, so maybe his explanation skipped that or I misunderstood.

I think it's likely the RMA tech just ignored the sticker because they're used to seeing such stickers, if "open box" really is a free for all. The RMA tech's job isn't to look for reasons that something is Newegg's fault, but rather to look for reasons that it is the customer's fault. As such, a sticker that usually means the board was repaired by isn't something to note, but thermal paste is. And then once that note has been made, that's all the phone agent is going to ever see.
Congrats on the launch - what you've built is incredibly cool.
When do you plan to add European investment accounts?

I cofounded Nordigen (Plaid competitor in Europe) and we use PSD2 bank connections, which are great for payments data but do not cover investment data, which is less than ideal. Aggregating OAuth APIs for European brokerages would make so much sense.
This is in stark contrast to the charter schools in NYC which are far better than all but the best regular public schools.
> he figured time syncing wasn't important enough to justify a daemon

Time synchronization is very arguable THE most important thing on a server (for numerous security related reasons).

How many moons ago was this incident? It's perhaps forgivable ignorance in the 90s... not so much today.
If I wanted to get into linux phone development, what's a good entry point into this?
This isn't really correct. They had extra material that they wanted to use - but the Army (get this) wanted to collect bombs after the first two, so they could use them to nuke the beaches prior to Americans landing there.

Yeah. a) they made the assumption that the nukes would not be enough, and b) planned for US soldiers to walk on post-bombing irradiated landings.
https://news.ycombinator.com/item?id=26639261
That is a different argument than doing nothing.