skysight-inc/HackerNews huggingface dataset:
> but I genuinely can't understand how anybody could look at the mess that's Rust's async and think that it was a good design for a language that already had the reputation of being very complicated to write.

Rust adopted the stackless coroutine model for async tasks based on its constraints, such as having a minimal runtime by default, not requiring heap allocations left and right, and being amenable to aggressive optimizations such as inlining. The function coloring problem ("contamination") is an unfortunate consequence. The Rust devs are currently working on an effects system to fix this. Missing features such as standard async traits, async functions in traits, and executor-agnosticism are also valid complaints. Considering Rust's strict backwards compatibility guarantee, some of these will take a long time.

I like to think of Rust's "async story" as a good analogue to Rust's "story" in general. The Rust devs work hard to deliver backwards compatible, efficient, performant features at the cost of programmer comfort (ballooning complexity, edge cases that don't compile, etc.) and compile time, mainly. Of course, they try to resolve the regressions too, but there's only so much that can be done after the fact. Those are just the tradeoffs the Rust language embodies, and at this point I don't expect anything more or less. I like Rust too, but there are many reasons others may not. The still-developing ecosystem is a prominent one.
Here are some links to images. Photographs of the setup:

https://ars.els-cdn.com/content/image/1-s2.0-S00167061230033...

And then various shapes:

https://ars.els-cdn.com/content/image/1-s2.0-S00167061230033...

https://ars.els-cdn.com/content/image/1-s2.0-S00167061230033...

Over time:

https://ars.els-cdn.com/content/image/1-s2.0-S00167061230033...
No, you'll have them because Texas (ahem, ERCOT) decided to isolate their power grid from the rest of the country.
You cancel a sync IO op similar to how you cancel an async one: have another task (i.e OS thread in this case) issue the cancellation. Select semantically spawns a task per case/variant and does something similar under the hood if cancellation is implemented.
I am a statistician, work in ML research
I don't know that it's necessarily outdated, more than it's a fork that evolved differently, and I don't think they'll reconverge.

I actively use ipfw and pf (at the same time!) because neither one can do all the things I need. I've never used the third one though.
Does that really buy you anything though? If they're willing to rescind offers, they'll be happy to lay you-off a few days into your employment too.
The dev cycle is slower, yes, but once it compiles, there is no debug cycle.
Hard to get tenure if that’s what you lead with!
In other words: you don't have to wait for slow read times if you don't bother reading the data at all!

You still need to live with the slow write times, though. What's the point of even building a single unit of tape storage if it will take you a minimum of 30 years to write your data to it? Why not just make 1 million smaller ones?
There’s another risk you’re not accounting for: Reputational damage.

The professional world is smaller than you think. A few years from now you may want a job with someone who works with someone who knows your old boss. They’ll ask for a reference because it’s so easy to find these connections in the era of LinkedIn. When someone leaves a company without notice, that tends to become the thing they’re remembered by. And it’s not a good look.

The risk of a rescinded offer is vanishingly small. Choosing to optimize to avoid that tiny risk in exchange for a near guarantee of damaging your reputation is not a good trade.
Buddy bradley.
Co-ops build stuff like this all the time in rural areas.
I live in SoCal and I have literally never had an order arrive open. They're usually sealed with tape. I don't have as many orders as you, but if it's that common I should've ran into it at least once by now
> They really do try to talk you out of it.

Who? Apple? I can't find any statements from them begging us not to use it. It's also a dumb argument since they can just --not-- release the feature if they don't want us to use it.
Well if that’s your concern lets start with proprietary remote repositories such as github and all the CI providers. That’s a lot more critical to the development process than a chat app.
that is wise, as long as you don't piss off your old colleagues as to not be able to get a reference later. or don't care.
I believe that people who are accustomed to this size of company, do in fact write out two dozen+ applications, each altered for the role that is listed, with BLOCK LETTER Position Identifier and Very Corporate personnel photo on each and every one. Despite the stupid amount of time it takes to do this, if you do not do this you will get zero jobs. ps- not me
Doordash has abandoned my orders and delivered food hours late. Hours.

Uber eats has never once had that issue in my area.
It looks like every project by default has a standing token with read privileges. It never expires and its not opt-in. Unless I’m missing something, that seems ridiculous.
The employer version of this is severance, not a notice period. Your logic is flawed.

Getting severance is better than a notice period anyway because you can get a new job and still get the money.
There is always a stark disconnect from the top and the people at the bottom or those who actually use the app.

Also, never had a problem with either DoorDash or Uber with food delivers.

> Uber's CEO says his time delivering food for his company revealed a "lack of quality" with its product from a driver's perspective.

Yes, everything is really nice and works great when you don't actually use the thing. I can't even find the words...

> "It wasn't a pleasant all-hands with the company, but it set a tone, and we set that expectation — we started celebrating employees going out there delivering, employees driving," he said. "It is a point of pride for employees now — when they drive they get a little badge on their corporate profile, etc."

God forbid you be an everyman.

Edit: I've now read it and removed "I haven't read the article but".
Electric Dreams (1984 Film)
This appears like a clever thing to say, but it just isn't true, and it's easy to verify.
I don't know any details other that it was about some trademark (maybe). Where can I read more about this?
xv6 was originally written for 32-bit x86; the RISC-V port is a relatively recent development. See e.g. https://github.com/mit-pdos/xv6-public for some of the earlier history.

rxv64 was written for a specific purpose: we had to ramp up professional engineers on both 64-bit x86_64 and kernel development in Rust; we were pointing them to the MIT materials, which at the time still focused on x86, but they were getting tripped up 32-bit-isms and the original PC peripherals (e.g., accessing the IDE disk via programmed IO). Interestingly, the non sequitur about C++ aside, porting to Rust exposed several bugs or omissions in the C original; fixes were contributed back to MIT and applied (and survived into the RISC-V port).

Oh, by the way, the use of the term "SMP" predates Intel's usage by decades.
You have enough info to build your own, then share it with us for free!
Google is failing me - what's the VC spin on HHVM?
that would be another level of douchebaggery, although probably not unprecedented
I just ran "a criminal" 8 times and got only white men.
Threads, at least on Linux, are much more lightweight than you seem to think. Async Rust can scale better, of course, but you're overexaggerating your case.
When you start finding people making generative AI models copying your art style.
The pet peeves (https://www.businessinsider.com/uber-drivers-worst-passenger...) bug me:

1) Tipping shouldn't happen. There should be a fair salary. Tipping was introduced in 2017, and Uber is trying to make it more common. If drivers should be paid more, it should raise fares and incomes.

2) Arriving late should be okay. Passengers should be charged for it at a rate fair to the driver. Especially arriving at an airport after a 16+ hour flight, I'm glad to pay a driver to wait.

A lot of this feels like misaligned incentives.
This.

I know that HN zeitgeist, weirdly, in some strange way likes to be "interchangeable cogs in a machine" (focus on standard easily employable tech stack, avoid learning company-specific stuff, change jobs frequently, be easily replaceable); but in a LOT of companies leaving with no notice puts everybody (coworkers, management, business, client - real human beings) in a crazy bad spot.

Many large companies have a checkbox on whether a leaving employee is rehireable. I've seen enough people leave then come back, that it may not always be as ok as it seems to burn those bridges - not to mention that in some ways industry is surprisingly "small" - people move and bad reputation spreads. If Bob asks Fatima who worked with James, should he hire him - you can bet this'll come up. And if that feels like a low hypothetical risk - it's a lot higher than risk of rescinded offers.
I don’t think rescinded offers are very common, certainly not as a percentage of job changes. While you are entitled to not give notice doing so puts your managers and coworkers in a bit of a lurch. This accumulates ill will that offsets all the work you did to generate good will. As your career advances your best way to find a good job is through your network of past managers and coworkers. Burning through your goodwill as some sort of social protest against the state of tech employment is certainly an option, but it’ll hinder your chances of getting greater roles of higher trust based on your reputation vs cold applying into places that don’t know you.

As a manager I’ve always asked people to go home immediately throughout my orgs, though. I appreciate when people offer notice and I’ll pay them for a period to be available if we need it, but ultimately:

* a dead body stinking up the team doesn’t help

* if you need someone for two weeks to transition work, you aren’t managing your teams well to begin with. Everyone should be important but no one should be indispensable.
The nerve of china. It's the US military's job to exploit US troops and veterans god dang it.
> Users who cannot afford new enough hardware to make the resource-intensive client pleasant to use are also left by the wayside.

Wait… people can’t run web browsers?
In 99% of the cases the candidate has exactly 0 leverage to negotiate this and the person on the other end will be laugh at this notion.

Instead of weird fantasies about power that doesn’t exist, how about we acknowledge the skewed relationship between a(n) (prospective) employee and an employer like the rest of the civilized world and do away with “fire at will”.

If something like this happens in the EU, then it’s likely the company would at least be on the hook to pay the salary for the duration of the initial contract that was signed (often 6 month minimum).
I say likely, because of minor variations between countries, but it’s a given in most countries.
LSP refers to the Language Server Protocol, a standardized protocol designed to provide real time source code information for a given code base; tree-sitter is parser design to create a real time syntax tree for a given source file.
No doubt the OP is suggesting the use of an Emacs plug-in based on those newer technologies.
So what exactly did they change?

The article says they had an unpleasant meeting…

It’s not clear to me that this story actually changed anything for the drivers… and the CEO doesn’t even know their pricing, makes me wonder how much he drove at all.
I have bad news concerning pop music.
> "It wasn't a pleasant all-hands with the company, but it set a tone, and we set that expectation — we started celebrating employees going out there delivering, employees driving," he said. "It is a point of pride for employees now — when they drive they get a little badge on their corporate profile, etc."

Oh sweet. A badge on a corporate profile
It's always over 100F in the summer everywhere. I've checked every day for the past two months all over Dallas.

NYC and SoCal isn't the whole country.
250 is not a big number... :(
Your comment was flagged for being full of shit. And you proved why.
This is an excellent discord, for starting discussions and getting help.
When folks enjoy it or it is thought provoking. The "art" gatekeeping is one of those things I will literally never understand.
> It is true that this needs to be done with some care otherwise you can end up infecting your whole codebase with the “workaround”

It's a "workaround" precisely because the language does not support it. My statement is correct - you cannot turn the borrow-checker off, and you pay a significant productivity penalty for no benefit. "Rc" can't detect cycles. ".clone()" doesn't work for complex data structures.
Anecdata: Spouse was let go from Salesforce in the January round of layoffs, after 2 years there. She received 6 months salary, was allowed to keep RSUs that would have vested within 90 days (which amounted to another ~2 months salary), and the company paid for COBRA for her and family for 6 months.

That was very generous, but it's not at all unheard of. There are people who were on her team who got more than 12 months. They had been there quite a bit longer.
> (well, i guess someone has to)

No, it really was unnecessary for you to do that. Most of your comment is snarky swipes that are not at all substantive. And pretending like this that xv6 didn't also target x86 is dishonest.
Works generated by AI are not copyrightable. If you take a generated work and substantially build upon it, then it's likely copyrightable.

At least that's the case for art, and I think the same logic should apply to art and code.
> ...the only correct response to which is to contact the state government and complain while continuing to respect the law. Breaking the law while remaining silent is diametrically opposed to the democratic system

No, this would take more hours than there are in a decade.
Non free software? Either this seems misleading or Im confused. You don’t need to pay to participate in the discord. The server owners may have costs but thats not a burden on the community and is always going to be the case.
Wildly false. Rust's design does virtually nothing to prevent logic errors.
That's just... Not even remotely true in my neck of the woods.

Everywhere I worked at:

- if individual is not performing, people spend months trying to help them gear up before even considering laying them off

- if large layoffs are happening, there's time and severance. Even the ones we see in the news and perceived as sudden and unfair, the notification may be unexpected, but you're rarely laid off effective tomorrow.
"Toy" is solver jargon that sort of means there's an alternative that blows it out of the water.
https://ars.els-cdn.com/content/image/1-s2.0-S00167061230033...
New catalyst decreases the energy required to split hydrogen gas from water
The qualified experts aren't the same people who set the limits. It's very common for a low speed limit to be "backed" by a professional report recommending a significantly higher limit.
In all seriousness it makes a lot of sense. If you drive 8 hours a day you could easily be paying $500/month for gas, which is the car payment on a used Tesla. Which you would then own after a few years and still not be paying for gas.
If you somehow are under California jurisdiction, the legal term you are looking for is called "promissory estoppel".

Being given a promise of a job may have put Flexport on the hook for damages.
How common do you think rescinded offers are?

You’re virtually guaranteed to burn your reputation among your former coworkers and ensure that the one thing they remember you for is taking a new job and giving negative one weeks of notice. Is that really worth avoiding the vanishingly small risk of a rescinded offer? Do you really think the old job wouldn’t let you keep working there if you gave 2 weeks’ notice and then rescinded your notice?

I think you’ve got your risk model backwards. If you optimize too much for rare outcomes, you start missing the bigger picture.
When other more established artists get inspired/copy.
At least methane burns with a visible flame in daylight.
>This model is entirely libre (free as in freedom), and can be used for any commercial or personal purpose. My only request is that you go forth and fill the world with SVGs.

Some people release OSS out of passion. Some release it out of pain.
> Guy, I don't know who you're upset with or why, but it's not me.

I'm not mad at ya. Just your stupidity.

> You know that just means the perils of being a minority in a democracy, right?

Hence why the US is a republic.

> What on earth are you talking about?

'It's funny how the foundation of modern democracy ( US ) was created on distrust of government and elites, but the 'democracies' that worship british royalties was founded on slavish worship of authority.'

Or you can play your silly and childish games.
I spoke to a driver and he said he leases car for $2xx a month.

He drives 10+ hours a day and had like 60k trips completed. I'm sure he is doing okay.
Uber actually encourages their drivers to drive Teslas, so even though it seems out of touch for him to say, "and then I bought a Tesla," it's more likely that he was going through the standard routine for an Uber driver. He could have been going through the car financing process and not paying outright with cash.

I vouched for your comment because it's accurate.

Sources:

https://www.uber.com/us/en/drive/vehicle-solutions/hertz/tes...

https://fortune.com/2022/06/28/uber-lfyt-gig-workers-teslas-...

https://www.uber.com/us/en/drive/services/electric/
This summer I had the chance to experience Uber in Europe as well as at home in Michigan. In Michigan the app might ask you to walk across the street as a convenience to the driver. It's rare but it happens.

But in Europe it might ask you to walk over a mile! I was careful (or so I thought) to find a place that made sense for the driver. But Uber wouldn't agree even if it meant getting picked up at a bus stop where by the time I arrived was already gone. I was always charged as the at fault party.

In Poland and the Czech Republic Uber was super cheap and I had some amazing conversations with the drivers but never knew if getting picked up would go smoothly or not.
A very cursory internet search shows that your history is entirely wrong:

https://agileforall.com/history-of-tdd-as-told-in-quotes/

Djikstra proposed the idea in the 1970s. Rails did not in any way pioneer TDD. They were very vocal about it but “[stood] on the shoulders of giants.”
https://en.wikipedia.org/wiki/BNSF_Railway

The BNSF Railway Company is the principal operating subsidiary of parent company Burlington Northern Santa Fe, LLC. Headquartered in Fort Worth, Texas, the railroad's parent company is a wholly owned subsidiary of Berkshire Hathaway, Inc., of Omaha, Nebraska.
To be fair, prices fluctuate a lot based on time of day. Just checked the price of a 2.7 mile ride to a restaurant I like in Brooklyn and an UberX is $17.90.
Wtf? They bought Atari age?
There's honey that we collect from wild bees from the ground. We had a hive? at home in the village which someone dug out. The honey looked darker compared to I suppose the commercial one.

I didn't see if the honey was in combs or what, so I'm curious how that would look on a render like the one in the article.
You're overstating your case. Rust's async tasks (based on stackless coroutines) and Go's goroutines (based on stackful coroutines) have important differences. Rust's design introduces function coloring (tentative solution in progress) but is much more suited for the bare-metal scene that C and C++ are famous for. Go's design has more overhead but, by virtue of not having colored functions, is simpler for programmers to write code for. Most things in computer science/programming involve tradeoffs. Also, Rust's async/await is built-in to the language. It's not a library implementation of stackless coroutines.
Uber's pricing is algorithmic and New York is on the exact opposite side of the country.
> the vast majority of IoT devices are not exposed to the internet

IoT stands for "internet of things". I am by no means an expert in the area, but my understanding was that am IoT device is by definition connected to the Internet.
An example of this is with the Sacklars. They're functionally no different than an illegal drug cartel, and yet they are spared criminal sanction. Any normal person or group of persons doing what they did would be in jail forever and have literally every cent taken from them. But the Sacklars/corp get away with a civil fine that keeps most of their wealth and more importantly, their freedom, on the table.
Definitely not "working", yeah, but

On MSVC, an all-zero string object is the correct representation for a std::string containing "" (and the memory leak is easy to miss if you don't do it too much).

On both Clang and gcc, an all-zero string object is not using the short-string optimization -- it is a string with size zero, capacity zero, and an external buffer of nullptr. (On clang this happens because capacity is even, and on gcc because &str->buf != &str). Any code that attempts to access its null terminator will dereference the null pointer and crash immediately.
Great article! In 2019 someone posted same thing: https://medium.com/@lukbebalduke/mtg-hivemind-artificial-int...

But sadly, he didn't keep going into it after that. Gladly, OP made huge progress on the same topic!
I think the super-hot job market in tech from 2012ish to 2022ish has really led a lot of people to underrate having a good professional reputation. When you were competing with 10 other companies to try to get a candidate, you couldn't be too fussy about "hey, why do you have a string of short tenures," or "did you get a kinda lukewarm reference from so-and-so."

So now we've got people saying, "Hey, don't worry at all about making your employer mad," in an environment which favors employers over employees. It's shortsighted, unless we return to ultra-hot job market in a year and this is a one-time difficulty.
No, the scammer stole someone’s credentials and the bank clawed back the payment. The bank can always reverse it at any point in the future. The consumer never, ever can.
How are the bordering regions of Czechia and Poland?

Do they have the same issues?

I assume the open border facilitates travel somewhat.
One thing I really like about rxv64 is pretty easy to be built on MacOS, without having to built a custom GCC, like the original xv6.

Of course, there are other various "Rust xv6" forks and unfortunately they won't compile with recent Rust...
also quite interesting to compare with other implementations from the present and the past:

https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c
https://github.com/freebsd/freebsd-src/blob/release/4.0.0/us...
> better fuel economy

that is, btw, the history of why we have a 55 speed limit. In 1973 there was a gas crisis, so in 1974 President Nixon drafted the National Maximum Speed Limit (NMSL), ostensibly to conserve gasoline.

https://en.wikipedia.org/wiki/National_Maximum_Speed_Law
Can I have a tiny fraction of it? I want a consumer tape drive, or the revival of Zip disk /MO Disk that is in TB rage that last a few hundred years.
> How is this at all different from how literally every hiring manager in the world thinks of themselves? Literally no one is going to wake up in the morning and think "wow, I'm OK with whiffing on a candidate for my team."

For some companies the job is "maintain the team at X people, so when we're below that hire the best people we can find in a reasonable time, and when we're above that we close hiring".
In western Virginia they sit at the bottom of hills and give tickets to out of state plates that go over the limit by any amount.
Yeah I get that.