skysight-inc/HackerNews huggingface dataset:
Sure, but you're also on video committing the crime in front of police officers. The lawyer isn't going to help you get out of the charge for not answering questions, and if they still want your passwords the judge will absolutely just order you to give them up and keep stacking prison sentences until you comply.
>Brandolini's law, also known as the bullshit asymmetry principle, is an internet adage coined in 2013 that emphasizes the effort of debunking misinformation, in comparison to the relative ease of creating it in the first place.

Or are you arguing that creating order is more easy than creating entropy? Because I'd like to see the physics behind that one.
I was a verbally precocious kid, and I swear C&H had at least a small hand in that.
Wittgenstein's Logic of Language
If Amazon delivers a late package I ask for a $5 credit, and I get it every time
Programming in Rust is really not like being in an abusive relationship. The compiler is trying to help out as much as possible, especially since rustc has the best error messages in the world.
If you're remotely sane, you'll always want memory safety. That's not really an optional property, because even in C/C++ compromising memory safety throws you straight into the land of nasal demons. The question is whether you want the compiler to ensure memory safety, or to do it completely on your own without language support.

Personally, I've never met anyone who can ensure memory safety in their C/C++ without onerous restrictions even more severe than those rust imposes, but maybe you're superhuman.
The problem is that use of unusual Unicode characters represents memes, there are constantly new ones and it would be hard for any screenreader to keep up with new stuff. And there are plenty of imaginative use of letters from Indian scripts, from hieroglyphics, etc. where the screenreader can’t be expected to recognize what is intended as easily as a human being would.
A little extra attack surface won't stop the vested interests from making sure that their code (tracking, ads, whatever other user hostilities) continues to run.
Nile: Serverless Postgres
ByteByteGo is one of the best YouTube channels I've come across. Really well done content, all explained very clearly.
>From my perspective every lifetime complaint the compiler has is a deeply appreciated hint that not only saves you countless hours of debugging down the line but also makes me feel confident/safe in the code

Meh, the fact that Rust's compiler is overly strict is just a truth (All compiling programs are valid, but not all valid programs are compiling), and I find it lowkey annoying that every time someone has a problem with it, rustceans jump to the defense to the point of almost denying the OPs experience.
I mean on a case by case basis it might simply be a difference of experiences and both are valid, but on a larger scale it does look like a bit of a pattern, at least to me.

Ofcourse, there restrictions aren't just a whim of a Rust core team (usually ;p ), and do come from practical limitations but regardless, it's fair to be frustrated at them.
That is what I figured, that it was for the benefit of people who would then take the coffee and walk with it on the way to work during the winter. However, they did this even when it wasn't winter...
I'll bite: what do you use instead?
This is my favorite bad lighting decision: https://www.carscoops.com/2021/09/left-no-the-other-left-min...

Turn signals that point the opposite direction of your intent.
A full 70% of security vulnerabilities are caused by memory safety issues. As professionals we need to get serious and have memory safety as a baseline requirement.
> And that part can be "design."

It's those design choices that are subject to all of the dilemmas that necessitate schools of thought such as those in "A Philosophy of Software Design". The mathematics hasn't been invented yet to determined the most efficient way to lay out complex software. And it won't be until long after our jobs are all replaced by fuzzy AI. Until then, software development is a performance art subject to many different schools of thought or philosophies of design, and you're fooling yourself if you think that you can escape from them.

At the end of the day, there is no mathematical formula to choose which color the border of a selected text-input should be: Only conventions, design philosophies, tastes and opinions.

The book you've linked (although I haven't read it all yet), provides a design philosophy for approaching a subset of the problems that computer programmers face. But: It doesn't have any writing on the hardest problems that programmers face in regards to IO and managing persistent state in a concurrent-access environment.
There's efforts to overhaul it, basically there's a lot of stuff that has to be more complicated (as you'd expect) if you want to add support for async somewhere, and understanding the error messages can be pretty mentally taxing when you get it wrong; and then there's a lot of cases where the async version of some pattern just doesn't work right now due to limitations in the compiler or the language itself, and hopefully it'll work someday, but in the meantime you need to use workarounds.
> After two decades of JavaScript and decent experience with Go, this is the most significant source of frustration and friction with Rust. It’s not an insurmountable problem, but you must always be ready to deal with the async monster when it rears its head. In other languages, async is almost invisible.

I am a former C and C++ programmer who lived calling into pthread almost every week for a decade. I use async rust everywhere now.

I don’t get the hate that async gets. In my opinion, everyone should be using async for everything. Including stuff that’s seemingly single threaded “simple” stuff.
The screen has to be there anyway for regulatory reasons.

The touch sensor itself is far cheaper than a bank of buttons.
You trust AWS? Seriously? Amazon?

What gets me is that AWS must have insane turnover with the Amazon stack ranking. The stability of that platform long term concerns me.

AWS is a utility at this point. Utilities are boring, conservative, and have people that know their systems and stay there for decades.
The reason we have protections and limits on the power is to /prevent/ the totalitarian state. You'd have to be seriously daft to to think of the next 5 country leaders, similar types to the last 5, /none/ of them would hold onto their power if they could despite becoming unpopular. Maintaining the fight against that is the opposite of believing it is inevitable. Once it happens prior rules no longer matter at all.

Again we limit power because it will corrupt and that's how we avoid totalitarian states. "This power grab is fine because we're not a totalitarian state" is utterly and dangerously moronic.
Thank you for ec2instances! I use it a lot and it's really great :)
And yet the big tech companies are perpetually re-writing their whole stack, or going out of their way to create new compilers for their language in order to lower their billing time.
>...which make your product worse and give your competitors an edge

I would find that argument passable if some of the biggest products from the largest companies functioned better. Performant software seems like a distant memory.
> I think the biggest thing is that the minimum extra spend if you want in house managed infra is basically the salary of a full time sysadmin + hardware costs.

The cloud promises to make admin tasks easier, however I have never seen it eliminate the role of a sysadmin in practice. In my experience, most organizations that run their infra on a cloud still have dedicated admin roles (often called "DevOps" or infra teams).

Hence, I think that the claim that a sysadmin's salary is an extra expense for self-managed infrastructure is exaggerated. You may need more sysadmins for achieving the same features in a self-managed setup compared to the cloud, but it is not a linear scale.
Second this. Lots of folks signed out of Apple ID (for good reason).
The more you look into it, the more it becomes apparent that Starship is optimized for launching very large constellations of LEO satellites, not for Mars colonization or even Moon missions. It's publicly pitched as a Mars colonization rocket because this pipe dream is the foundation of SpaceX's recruiting strategy. (It's easier to motivate rocket engineers with the dream of Mars colonies than with SDI contracts.)
if this works you can have all my money. stellar work in advance ohhhh do I dare even hope?

edit: sorry realize my comment is confusing, I got very emotional when I saw about flow storm http://www.flow-storm.org/

clojurescript debugging.. oh my god I can't even imagine.
It would be nice if the title weren’t framed in the reflexive, something like: “Dunkin Donuts settles with coffee burn victim for $3 million”
Kagi.com, a $10/month search engine, has "lenses" that "focus" your search. One of the lenses is "recipe sites that are high quality and don't have loads of useless crap"
I mean... that's not really the pain that people are referring to when they are struggling with async Rust, especially when you compare it other languages like JavaScript that also have a difference between async and regular functions.
> figuring out project management and infrastructure management feel incredibly weird

It's not just you, and the situation is worse than if they had no configuration management offering because, as Google is wont to do, they have several of them in various states of disrepair

- they cite terraform as their go-to deployment solution in damn near every blog post, but if you're trying to create something for (new users | deployment into _someone else's project_) the instructions start with "well, open a Terminal and ..."

- they now have some kind of "hosted terraform runner + state" whose name escapes me but is hiding somewhere in this list of a bazillion similarly named Cloud Somethings https://cloud.google.com/products?hl=en#section-14 ("Infrastructure Manager" is the one I was trying to think of https://news.ycombinator.com/item?id=37548639 and is, ha ha, not on that products page which is why I could not find it)

- they started to have a CloudFormation replacement with Deployment Manager <https://cloud.google.com/deployment-manager/docs/configurati...> but, again, I cannot stress enough how GODDAMN STUPID this is: one must enable deployment manager to use it, and the way one does that is via gcloud, click ops <https://console.cloud.google.com/apis/library/deploymentmana...>, or terraform -- then, ha ha, you went through all that trouble but you can't create an IAM Role with it <https://cloud.google.com/deployment-manager/docs/configurati...> partially because it's not a supported resource type and partially because MUTATING ROLE BINDINGS IS A RACE-CONDITION EVENT

And speaking of, there is, of course, no way to enable project services via Deployment Manager, so pound sand if your Project was not already carefully configured in advance of Deployment Manager

- cloud shell tutorials, which is basically the union of all of those: https://cloud.google.com/shell/docs/cloud-shell-tutorials/ov... although in that case they do actually go out of their way to allow one to create a Project, with the activated service APIs, during the tutorial: https://cloud.google.com/shell/docs/cloud-shell-tutorials/di...
Working on this project would be cool. Could tell all your friends about engineering peanut butter and its tolerances.
I think he wants them to be treated differently for some reason.
Did you mean non-GC languages? GC languages by default have at least memory safety because the GC frees for you when an object is detected to no longer be accessible.
The last time I did we did a WiFi password change at my house there were near 100 devices that had to be updated. Such a hassle. Thankfully it's stayed the same over 4 routers and about 7 years.
Because there is a whole industry around hyping PKM systems and note taking systems with pretty weak evidence to support their actual utility. Calling them essential creates the impression that those not using them are deficient.

Yet, given that people are both massively productive with and without these systems, it really calls into question the effusive marketing and community promotion of these tools.

I use obsidian everyday, but I recognize that I could do just as well with some other tool. It's preferential, not essential.

Exaggeration is not necessary for communication of value.
> A good C compiler does this when you turn on all the flags. I like languages/compilers that let you selectively disable the screaming and let you write bad code on purpose. Bad code that works but can be written fast is often better than perfect code that takes forever to write. Once you have a bad but working POC, you can make it less bad.

Rust supports that. Just mark everything unsafe.
> Do you need memory safety guarantees?

Is that better?
Disclaimer work at AWS.

I'm still trying to understand the scaling story better. When we say serverless it mentions automatically scaling when it detects some sense of resource pressure. If I have a "hot tenant-database", does that mean this shard will be scaled automatically without impact to existing queries? Or would there be some "blip". I suppose it's unavoidable in edge cases but curious about the regular ones as well.

It's an incredibly cool CX you have here with the automated query routing/tenancy story though, looking forward to what happens in this space.
Javascript to Rust is a big step for sure. It's probably a less painful journey if you already have a background in Typescript/C++. This article has good feedback though and I hope the language evolves to address some of it in the future.
A null pointer exception is a bug that breaks business logic. There's no "business logic instead of language stuff" because the language stuff is the foundation that business logic rests on. If you don't test against failure modes, what's even the point in testing?
I sometimes ground my chair through a 1-meg resistor when I'm feeling zaps during dry winter months. Also, run some copper tape along front edge of workbench, through 1-meg to ground, as a place to conveniently touch.

My bout with damaged chips was when I was programming early EPROM microcontrollers, and a zapped chip bore a strong resemblance to a firmware bug, so it was a frustrating time until I discovered the actual cause.
This sounds entirely scalable?
you can also use ublock origin to filter html to create a dark mode:

https://gist.github.com/aclarknexient/c39c83f2f97c3c6b1c307c...
The Beginning of Infinite Regress
If the first were true, I doubt Russia would be spending so much in the way of resources on simple territorial expansion (with the implicit long term expense of huge resources governing the conquered/occupied territory).

The invasion isn’t good ROI for them otherwise, even if it went well, which it does not appear to be.

I think the USSR restoration empire building narrative is overblown.

Also, if what you say about red lines were true, the US would
not be so hesitant to provide lots of advanced aircraft to Ukraine, which they have not done as yet despite this clearly being a full enemy-of-my-enemy proxy war.

Signs point to everyone trying to avoid escalation.
It’s not just that. There’s a few big problems with Rust async aside from the normal coloring problem that is inherent to async and not worth talking about.

* The async runtime and async functions are decomposed but tightly coupled. That means while you could swap out runtimes, a crate built against one runtime can’t generally be used with another unless explicitly designed to support multiple. I believe C++ has a similar problem but no other major language I’m aware of has this problem - that’s typically because there’s only a single runtime and it’s embedded in the language. Things like timers and I/O are not interoperable because the API you use has to be for the runtime you’re running under. I believe there’s work ongoing to try to remedy this although in practice I think that’s difficult (eg what if you’re using a crate relying on epoll-based APIs but the runtime is io_uring).

* async in traits. I believe that’s coming this year although the extra boxing it forces to make that work makes that not something 0-cost you can adopt in a super hot path.

* async requires pinned types which makes things very complex to manage and is a uniquely Rust concept (in fact I read a conceptually better alternative proposal for how to have solved the pin/unpin problem on HN not too long ago, but that ship has long sailed I fear).

* The borrow checker doesn’t know if your async function is running on a work stealing runtime or not which means there’s a lot more hoop jumping via unsafe if you want optimal performance.

* async functions are lazy and require polling before they do anything. That can be a bit surprising and require weird patterns.

Don’t get me wrong. The effing-mad crate is a fantastic demonstration of the power of algebraic effects to comprehensively solve coloring issues (async, failability, etc). But I think there’s stuff with runtime interop that’s also important. I don’t think anyone is yet seriously tackling improving the borrow checker for thread per core async.
GCP will shutdown your production servers and take one whole week to get it back. All for missing out on a KYC form.

Our story:
https://news.ycombinator.com/item?id=35133917

Forget about the initial shutdown, how can you take 1 whole week to resolve something critical like this.

Even if Google is offering me $1mil cloud credits today I wouldn't risk my business with them anymore.
>I long for a new company exploring the fringe of such phenomena, something like Sony did with ESPER (google it, it’s a nice rabbit hole).

Followed your advice but could find nothing except repeat mentions of the Xperia phone (thanks Google, because obviously ESPER is the same thing as Xperia...)

Care to share a link maybe?
> The market doesn't want this though.

I'm not so sure - I guess at least in Germany most people drive their 10 year old car as far as possible and don't even have the money to buy a new SUV.

I'm in my 30ies and most of my friends don't have a car, we drive a 2004 Mazda that we inherited and that is shared with the wider family.

A simple, well-designed usable EV for 20k€ or less might be something me and my friends buy.

Big SUVs and luxery cars might sell well because most people are just priced out of the market.

Used cars have insane prices - same as new after a few years.

There is nothing like the Golf II, even a Polo is more expensive then the Golf at the time.

I don't get it we have huge weight that requires huge batteries and tons of software and sensors and systems - substract everything that's not mandatory or required for security and optimize for weight and range - I can't imagine it's impossible. Max speed 140km/h would also be more than enough. There must be some tradeoffs without compromising security that get the most out of the idea of an EV. 20 years ago we had the Audi A2 that had a usage of just 3-4L/100km will all the improvement in simulation and material science there must be a way. Now everyone is moving two tons around in these big SUVs...
Square free … there’s a name I haven’t heard in a long time.

They had a simple wysiwyg in the browser html editor, in the pre-Ajax era.
I think you're right about single vs. 2+ lanes. It doesn't matter how many diagram signs they put up before the roundabout entry, people will NOT understand a roundabout with more than one lane, and under no circumstance will people going straight through realize they have to yield to someone coming from the opposite side who's going 270° around the circle and exiting from the inner lane.

Roundabouts are fine if the rule is, "Just get in there without hitting anybody and go around until you're ready to leave," but expecting anything more than that from most drivers is a lost cause.
I don't see how this can possibly be true given that people are successful without log books.
Sadly, there is no SRM for the dollar.
Yep shutdown our production servers and take 1 whole week to get it resolved. Nothing fraudulent on our end. Just missing out on KYC form.
I'm learning Rust because it seems clear that it's going to be important professionally. I wish I loved it, I really do. I see the benefits. But, at least so far, it's one of the most unpleasant languages I've used. I keep hoping that as I gain proficiency, I'll stop disliking it, but as I climb higher on the learning curve, I'm not really warming to it.

It's fine. It won't be the only language I'll be proficient in while being averse to it at the same time. But I heard so many people proclaiming their love for it that I expected to enjoy it, too.
They may be part of the course set, but they're probably not required or pathway classes.

I know, for the UCs at least, you would need to do some solid Java or C++ classwork, along with algorithms/data structures and machine language, at minimum. Unless things have changed drastically in the past few years, there's no way you're getting a CS degree at one of those universities coasting exclusively on UX, project management, interactivity theory, etc; those are electives to broaden your knowledgebase or specialize.

Edit - for instance, this is UCLA's core courseload for a CS BS:

https://catalog.registrar.ucla.edu/major/2022/computerscienc...

All of the aforementioned are required, even for a project management focus.
Draw.io is used everywhere. I see it all over in different enterprises...
Never got used to clips. Got 2 hyperbikes recently and had real trouble to get something like these https://www.indoorcycling.org/welgo-spd-kombipedale-mit-koer... , https://www.permanent-fahrrad.de/Retro-Fahrrad-Pedale-mit-Pe... attached to them, or get them at all. Because I'm used to them.

I know them as 'Tretkorb'. How do you call them, toe clips?

After about 20 years pause, only using an antique 'citybike' with three-spead gear hub and coaster brake.

It feels like I can fly again! :-)
Netflix on PS3: Disc-Free Next Week (2010)
Has Google killed Cloud services people relied on? I am asking in good faith as I don't know.

Whether Google kills random small-traction consumer products is kind of orthogonal to the Cloud question. If Amazon retail discontinues some Amazon Basics product, we don't read into that for AWS.
From the abstract, it sounds more like a toolkit for "Interactive / Hypermedia" papers. The paper itself is still dead.

I was hoping more for "Living" as in "active, uncertain, will grow over time".

A toolkit for expressing the research from beginning to the end - the state of the world as you understand it, highlighting the key uncertainties and experiments, and mechanisms for viewing the history.

As a motivating example for the type of "living research paper" that I'm thinking of, think of long-running software design decisions a la the implementation of `async/await` in rust.
I don't see how calling into question either exaggerated or ambiguous claims in a neutral tone is being a jerk.
I've found it really handy to just have a local Python webserver running on my workstation. Then my bookmarklets can just hit eg http://localhost:8000/cgi-bin/script.py to modify a local file or open up my notes for a certain Jira ticket or whatever else I can think of. There are security considerations with that approach though, since any random site you load can start sending requests to your local webserver.
So we shouldn't use Rust at all, since Rust is not completely memory safe since it let's you disable the borrow checker. We should be serious as professionals and use safe languages like Java, JS, Python, etc.

But of course there are use cases where you need memory safety guarantees and bare metal performance. In those cases, sacrificing some memory safety by using Rust is an acceptable tradeoff I think.