skysight-inc/HackerNews huggingface dataset:
> They can afford to buy in bulk when stuff is on sale, they can afford to store bulk supplies without them going bad, they can afford to drive a lot just to get the best deals.

In my experience, none of those three are that key at food cost cutting anyway. The key is choosing what to eat. If you make food at home out of cheap, nutritious ingredients, you will do well. The bag of beans that is only 1 lb and is at the expensive convenience store, is a much better deal than the 40 lb Costco crate of frozen pizza or something.

Beans, rice, potatos, eggs, oats. Start with staples like these and it really doesn't matter whether you are getting the name brand or the bulk discount....

> and lack of anything that resembles a decent food culture.

...ah, but here's the problem. If your food culture consists of habits around pizza and burgers, around eating fast food and heating frozen things in microwaves ..... if you never even learned to cook beans, in fact, never learned to even enjoy them and are grossed out by them, if you have no idea how to make a raw potato edible and delicious in 5 minutes.... then... yeah, you won't have any good mental "software" to help you easily feed yourself with stuff like the aforementioned. Instead you'll have to expend valuable time and energy on experimenting and learning new habits and recipes. Until you spend that time you are locked out of the cheaper food and locked into the expensive processed food trap.

> I'm sick and fucking tired of all of that. Fix poverty instead of patronizing those who are in direst needs.

And I'm sick and tired of both sides of this argument. Yes, fix poverty rather than patronizing thoese in need -- but acnowledge the real poverty is primarily cultural, not monetary, and tailor solutions to that, by somehow helping people relearn cultural food skills that were lost during the 20th century industrialization program.
I’m not pointing at a contemporary akin to Ford or Edsel. I’m pointing at people today using the latest versions of these tools today making the same class of mistake as someone might have made 4 or 5 decades ago. The tool is the problem.
Even then you actually lack the computing power and data to create these models in the first place. When this power is centralized it can essentially control what goes into the models output.
It's an interesting report, but it has too much loaded language, totally misses what the USSR manufacturing was intertwined between it's republics and whoever made the graphs should be shot.
> If we assume that the Japanese government's official view married women in japan without children as a dependent family members, then it is possible that immigration of foreign husband of those are an intended feature.

It absolutely is an intended feature - in part in order to make it easier for those women to have children, and in part so that they don't have to be supported by the state. Neither of those apply to OP's situation.

> It might also be that husband supporting such dependent family member is assumed to fall within the skilled labor category of immigrants.

It isn't. The visa deliberately allows doing any kind of work, including work for which it's impossible to get a work visa.
So many countries still have data caps, even the supposedly 1st world countries.

Even without hollywood people wouldn't have wanted to use any platform that uses their data and battery/power to share to everyone else.

It's the main reason why torrenting platforms have introduced ratios and made it hard to get invited.
Microsoft security hacking incidents worry US customers – report
It's my favourite part, except maybe debugging. I really like getting into the guts of an issue and working out why it happens which I suppose will be around for a while yet with AI code. It's a lot less fun with transient network issues and such though.
The page in question predates the founding of YouTube by ~3 years. It's in the middle of the Geocities time period, back when video distribution on the Internet was probably via Usenet and digital photography was probably on a Sony Mavica writing to floppy disks - or maybe to compact CDR if you were lucky.
livejournal.com sent me a virtual gift for my 20 years anniversary -- I had created the account in 2004
Before you go changing anything, I'd go talk to all the people who are there - understand where they came from, how the systems got to where they are, why they made their decisions, what they like and dislike, and what their biggest complaints are as well as what they love.

Then look at solving their actual problems. Because if you just come in and declare how you want it to be, you aren't improving their experience, you are just inflicting your own preferences on an existing ecosystem.

Dev experience is about people, not tech. You will use tech to improve it, but your devs are your customers - talk to them.
You are arguing they should have been forced to pay 58k for unnecessary site improvements when each place has a phone line that can be called. They did have alt text but it was deemed not good enough. What real value did disabled customers miss out on?
300lbs of counterweights strapped to the doors would take up a good bit of space. Pulley systems would need to either be 1 to 1 or would need some space to fall below the garage floor or to be stored above garage door height.

They seem far safer, longer lasting, and cheaper and easier to repair than springs, but are more expensive to install, take up more space, and probably cost more all in all compared to springs.

I found this that also goes into it:

https://engineering.stackexchange.com/questions/8692/why-are...
I reread Ursula K LeGuin's Earthsea Trilogy during a really difficult time in my life. I hadn't read them since I was a teenager. They are simple to read, but deep, with themes of regret and hopelessness but also perseverance and grace. I find her attitude toward her characters to be both brutally honest and compassionate. I think I got more out of reading these books as an adult at that time, although they were among my favorite books as a kid.
If I can tack onto this, "Hard-boiled Wonderland" by Murakami was one of the most fun and engaging books I've read in the last decade.
Bjarne Stroustrup: Remember the Vasa! (2018)
https://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0977r0...

Bjarne Stroustrup 2018: We are on a path to disaster though enthusiasm and design-by-committee (or rather “design-by-committees”). During the early days of WG21 the story of the Vasa was popular as warning against overelaboration (from 1992):

“Please also understand that there are dozens of reasonable extensions and changes being proposed. If every extension that is reasonably well-defined, clean and general, and would make life easier for a couple of hundred or couple of thousand C++ programmers were accepted, the language would more than double in size. We do not think this would be an advantage to the C++ community.”

“We often remind ourselves of the good ship Vasa. It was to be the pride of the Swedish navy and was built to be the biggest and most beautiful battleship ever. Unfortunately, to accommodate enough statues and guns it underwent major redesigns and extension during construction. The result was that it only made it half way across Stockholm harbor before a gust of wind blew it over and it sank killing about 50 people.”

“It has been raised and you can now see it in a museum in Stockholm. It is a beauty to behold - far more beautiful at the time than its unextended first design and far more beautiful today than if it had suffered the usual fate of a 17th century battle ship -- but that is no consolation to its designer, builders, and intended users.”
Boy do I have some codebases I could show you. I mean, the biggest problem isn’t that they’re written in C++, but it really didn’t help either.
For some context, there was a Supreme Court case at oral arguments today

Murthy v. Missouri (social media & govt - alleged coercion & collusion during covid)

https://www.politico.com/news/2024/03/18/supreme-court-murth...

https://www.youtube.com/watch?v=q0TjQaI0Rr0

https://en.m.wikipedia.org/wiki/Murthy_v._Missouri

https://www.scotusblog.com/case-files/cases/murthy-v-missour...

https://www.supremecourt.gov/search.aspx?filename=/docket/do...
There are a few outposts of The Kebab Shop (https://thekebabshop.com/locations/), and here in San Jose California area there are a lot of Mediterranean restaurants selling shwarma.
From the perspective of the programmer, true. Not necessarily from the perspective of the manager/customer, who can say in broad terms what needs to be done, and the programmer-black-box spits something out.
Fireproof

https://use-fireproof.com/

Pure JS embedded Document DB, no setup or config. e2e encryption, CRDT support. Build, prototype, iterate without a backend, plug into any cloud when you’re ready

[disclaimer: I’m part of the team working on this]
Building a house doesn't require using cheaper but more dangerous materials either but people try to, that's why we have regulations.

Analogies can be pithy but are rarely useful as an argument. Talk about reality.
Think of it more like a constraint satisfaction problem, rather than an optimization problem. There's no such thing as "the best" carrer, but there are lots of carrers which would be successful.

Also, its rare for a career to last more than 10-15 years these days, so think about how one career can set you up for another (e.g. 5-10 years programming, then move into management, or go back and get master's degree and teach, etc)
That's exactly what I'm saying below - PE is still very high, hence projecting the past growth into the future. But the scale changed a bit. A 37 PE ratio is extremely high by historical standards - this was reserved for very promising, small startups. Not for 2T companies. I know this got distorted in the past 15 years by abnormally low interest rates, but sooner or later it will come back to something that makes sense.

Buying long-term put options on Nvidia now is extremely expensive - the stock was so volatile that the price you pay for those options almost annihilate any gains you could expect, even if the stock losses 50% in 12 months.

You got me curious about those 5-7 trillions. Where these numbers come from ?
Canonical’s culture [1] is the antithesis of what nvidia wants.

[1] https://www.reddit.com/r/recruitinghell/comments/1bec2zk/lit...
Evidence we are not good at finding brain abnormalities.
Youtube has the esoteric folk people and I love it. Not big digressors, just really diverse and into their thing.
Woah, not bad.
Thanks - I'm in New Zealand where we only banned it in 2016 and I didn't know about EU rules.

It seems unlikely that Lambo would use asbestos. I had made an off-the-cuff bet against a pig-headed acquantance that asbestos brakes were banned here before I knew anything. He rang up his mate with a Lambo who had some other story!

NZ has some import exceptions but it looks to me that the exceptions are mostly for something like QC training kits for recognising asbestos: https://www.worksafe.govt.nz/topic-and-industry/asbestos/imp...
He seems to be in denial. I watched Stroustrup's CppCon 2023 talk about safety[0] a few months back. He spends about an hour talking about how important safety is and all the new things C++ offers to write safe code. Why did he suddenly start caring about safety now?

C++ is like a mad hatter's bad acid trip and somehow people are convinced it's still a great language to use in 2024.

[0]: https://www.youtube.com/watch?v=I8UvQKvOSSw
Also there's nothing to transfer and lose, assuming you don't drop the plate, any built plate just continues until it's complete, no messy papers to move and try to keep associated with what plates. The waiter bringing the order to the table can QA it and pick the right plates.

It's kind of genius.
Has 'Technical Debt' become a formal term now?
Doesn't this encoding scheme seem extremely brittle to errors during operation?

Like for example, you put the jelly pack at 12 o'clock, and then if someone rotates the plate, now it's at 6 o'clock and you have the wrong meat for the order.

Or, someone simply bumps into the plate and the packet slides to the other side. Even if you bumped it and it did not slide, you could not verify that it did not slide.

My general take away here is that someone tried to invent a new language basically (pictographic). And english (pen/paper) was probably sufficient? Inventing new languages (and having everyone learn them) is extremely hard.

Edit: btw, I've eaten at waffle house several times, although it was 10+ years ago when I was regular. They did frequently get my order wrong by forgetting things. I don't think it was attributable to this encoding scheme (one time the waiter tried to memorize the whole order and simply failed)
> The first step to solving a problem is accepting reality.

Ok, the first thing I’d like to accept is that C++ is just not safe enough for most applications. And yes—you also can’t throw C++ in the garbage.

Both of those statement are part of our reality—C++ is unsafe, and we will use it anyway. That’s why we solve this problem on two fronts. First, we advise programmers to ditch C++ for safer languages, when reasonable, because C++ isn’t safe enough for most needs. Second, we invest a lot of energy into making C++ safer, with better tools, safer libraries, changes to compilers, static analysis, run-time instrumentation, etc. It won’t close the gap—C++ is still unsafe and will be for the foreseeable future—but it will make a big difference to the people who, for whatever reasons, still use C++ despite its safety problems.

The C++ FAQ has a better picture here:

https://isocpp.org/wiki/faq/big-picture

> In 99% of the cases, programming language selection is dominated by business considerations, not by technical considerations. Things that really end up mattering are things like availability of a programming environment for the development machine, availability of runtime environment(s) for the deployment machine(s), licensing/legal issues of the runtime and/or development environments, availability of trained developers, availability of consulting services, and corporate culture/politics. These business considerations generally play a much greater role than compile time performance, runtime performance, static vs. dynamic typing, static vs. dynamic binding, etc.

There are a lot of good reasons to use C++. C++ is also unsafe. Both are true.

We don’t need to write long apologia explaining why C++ is actually safe, and you shouldn’t be looking at legacy code, or you need to hire better programmers, or you’re using the wrong tools or wrong practices or something like that. Ultimately, those arguments don’t withstand scrutiny.
I wonder if longer life springs could be made from something like chrome silicon, or if the application of force won't work that way for that material.
Can C++ be safe? Absolutely! Does a jr. developer know how to avoid all the pitfalls and craft this magical, safe code? No examples can be shown.
Do you mean Polars depends on/uses DuckDB pretty heavily in Rust? I'm only just now dabbling in Rust myself so I'm not familiar.
It's so weird it's taking them so long, because as far as anyone can tell AMD is mostly competent enough to make GPUs within some percentage points of Nvidia, the "breadth of complexity" in what these things do at the end of the day is ... rather underwhelming, the software stack may appear to be changing all the time but is also distinctly JavaScript-frotend-esque... is there an insider that knows what the holdup is? Is AMD just averse to making a ton of money?

At this point AMD investors should be rebelling, it's pissing money out there but they are not getting wet, and management might have doubled the stock price but that's little consolation if "order of magnitude" is what could have been.
They don't want to cannibalize sales of the super-expensive GPUs dedicated to ML/AI.

5090 likely won't have more than 32 GB, if even that much.
In 1958 35,000 people died on American roads. Last year, 43,000. So yeah, cars have gotten safer at about the rate that C++ has.
Ironically, Margaret Hamilton _was_ able to produce a bug free program back in the 60s. However, no-one is seriously considering replicating her techniques because they (some of them, ant least) are way too expensive for modern software.
Except for the un-implemented features which they might need.

It also uses serializable isolation and in their implementation reads are blocked by writes unlike in Postgres. Those are both significant changes that can have far reaching application impacts
Vastly more electricity has been supplied by hydro. Nuclear is tiny.
> If only people were perfect, then things would be perfect.

That argument doesn't hold up too well, considering that people are involved either way.
> Before you were saying, "WebSockets lack flow control (backpressure) and multiplexing, so if you need them you either roll your own or use something similar to RSocket.", and now you're saying you can't roll your own? ;-)

You can, but you need to do it at the application level, which is a lot more involved. It would be nice if it were as simple as checking if bufferAmount > some threshold and then waiting on a promise before attempting to send again. That's essentially what you get with ReadableStream and WritableStream, which are provided by WebTransport.

> Erm, HTTP2 & HTTP 1.1 have their own problems, some of which you yourself have identified. We actually rolled back from HTTP2 to HTTP 1.1 because of problems with HTTP2, particularly with mobile performance.

Not sure if we're actually disagreeing here. In any case, we can both agree HTTP2 is not a panacea, and actually worse than HTTP/1.1 in some cases.

> That said, adoption of HTTP3 seems to be about half that of HTTP2 right now. Not bad for a brand new protocol, but I'd say we still have a significant amount of time to go before HTTP3 is the dominant protocol.

Here here. Overall I'm bullish on HTTP3 in the long run. I really just hope random enterprise networks don't decide to block it. In any case, it's going to be a big win for the places where it works.
Even such basics as initialization is full of traps in C++, its truly language thats awful to produce anything safe with. C on the other hand isnt a bad language, but C's problem comes from the horrible standard library and bad standard. You can create much better C by passing -fno-strict-aliasing -ftrapv -fsigned-char to the compiler even now. Heck rust's unsafe is more unsafe than C. "C" could be improved with a better compiler that ignores the standard, but perhaps it wouldnt be C anymore even if the syntax remained the same.

C++ problem is not helped by the compilers either, shoutouts to msvc++ accepting absolutely wrong and horrible code by default.
This was a really entertaining read. Wishing the author the best of luck.
"Requires". It will rely on the honor system, which sleazy assholes won't honor; or the report system, which people will abuse. AI detectors aren't reliable; GenAI is basically tautologically defined as hard/impossible to detect and we keep getting reminded that "it will only get better".

Everyone calls this a problem, but it's a predicament because it has NO solution, and I have nothing but contempt for everyone who made it reality.
The lock-in is more of a bonus for them. The underlying problem is that it's impossible to build a chip big enough, or even a collection of chiplets big enough. Training LLMs requires more silicon than can fit on one PCB, so they need an interconnect that is as fast as possible. With interconnect bandwidth as a critical bottleneck, they're not going to wait around for the industry to standardize on a suitable interconnect when they can build what they need to be ready to ship alongside the chips they need to connect.
> Anti-disinformation groups talk endlessly about building “resilience” to disinformation (which in practice means making sure the public hears approved narratives so often that anything else seems frightening or repellent), and audiences are trained to question not only the need for checks and balances, but competition. Competition is increasingly frowned upon not just in the “marketplace of ideas” (an idea itself more and more often described as outdated), but in the traditional capitalist sense.

The lack of competition is bad, bbut so is the lack of spectrum. That is, if there is competition it's typically dumb'ed down to binary, with all nuance, subtitles and perhaps contradictions are removed. What's often left can't be won by either side. But perhaps that's exactly the point?
C++ is an unsafe language in all of its current implementations except CHERI.

Stroustrup is being tone deaf or maybe he just doesn’t get it.

The issue is that there are so many ways in which you could write a C++ expression that violates memory safety and gives users control of your heap.

In Java or other truly safe languages, there are zero ways to do that short of pwning the JVM with a bug. In Rust and other safe systems languages, to do something unsafe you have to call it out using the unsafe keyword.

So - the places in your C++ code where you might have a memory safety violation are everywhere while in the alternatives they are either nowhere or they are carefully demarcated.
The EventSource API (the browser "client API" for Server-Sent Events) leaves a lot to be desired. While I am a maintainer of the most used EventSource polyfill[1], I've recently started a new project that aims to be a modern take on what an EventSource client could be: https://github.com/rexxars/eventsource-client.

Beyond handling the custom headers aspect, it also supports any request method (POST, PATCH..), allows you to include a request body, allows subscribing to any named event (the EventSource `onmessage` vs `on('named event')` is very confusing), as well as setting an initial last event ID (which can be helpful when restoring state after a reload or similar). And you can use it as an async iterator.

I love the simplicity of Server-Sent Events, but the `EventSource` API seem to me like a rushed implementation that just kinda stuck around.

[1]: https://github.com/eventsource/eventsource
It's a weird graph... It's specifically tokens per GPU but the x-axis is "interactivity per second", so the y-axis is including Blackwell being twice the size and also the increase from fp8 -> fp4, note it will needs to be counted multiple time as half as much data is needed to be going through the networks as well.
This is the part where I disagree:

> Business logic must always be defined in an unambiguous format

No. That’s only the case because unambiguous ‘business logic’ is what we have to use when trying to explain to rigid, unthinking machines how we want our business to operate. Business processes aren’t naturally rigid. Computerization has just made us think that they have to be.

What LLMs have the potential to do is to replace rigid unthinking machines with fuzzy contextually aware machines. Instead of emulating mindless bureaucrats only capable of operating on the rigid record formats of their strict filing systems, who’ll reject any form that contains a single error, as computer programs do today, future systems with a grasp on fuzzier language might be able to work with more ambiguity.
I agree, but I also disagree.

The concept with firebase DB's is flawed IMO, I never got the point of directly accessing a DB in the frontend, or allowing that even with security rules, it just seems like it would cause problems.
Nvidia Announces GR00T, a Foundation Model for Humanoids
Can you clarify a bit? Why are they valuable ad slots? Why wouldn't I call the vendor that installed my opener to repair it?