skysight-inc/HackerNews huggingface dataset:
The Public Procurement Revolution: How Technology Redefines Government Spending
Up Up Down Down Left Right Left Right B a Start
From that link, "that is only 0.15% of the working population" and nearly half of those workers are teenagers, i.e. it's a first-time, likely part-time job.

I stand by my claim that (essentially) nobody is working for minimum wage in 2024.
The problem is they are using a catapult.... If they were using a trebuchet they would have no issues.
What about just launching up drones with big batteries to pretty respectable altitudes, that can then go e-refuel other drones?

Air power delivery has been a long little "wouldn't it be cool" notion for me. This just feels like it could be a good way to boost this idea, get it off the ground. Ok sorry about that.
Why is generics the tricky bit? Isn't that the bread-and-butter of this type system? You should just be able to substitute the term 'type variable' in the article for 'generics'.
My point is that if the capability of your aerobic system is very poor - and it is for the vast majority of people, including many HIIT advocates - then whatever exercise you do, you'll very quickly be approaching anearobic territory and find it very difficult to stay at a metabolic steady state for long durations of exercise. When I mean anaerobic, I don't mean "zone 5". I just mean that there will be a much higher percentage of anaerobic glycolysis happening than perhaps should be for a particular level of exertion.

For these people, their aerobic system is so bad that they need to walk to stay in "zone 2". It stands to reason that if they are doing a HIIT session then they are very quickly in the territory of zones 3 and 4, so we are looking at lactate threshold or critical power levels of exertion. So you are looking at more than 60-70% of power coming from anaerobic metabolism. That puts a lot of stress on the body.

For these people to develop their aerobic systems, they need to do a lot of slow jogging or fast walking. Eventually if they do that enough then they'll be much healthier, find HIIT sessions easier and recover much faster. People that spend too much time doing intense exercise will eventually end up with some degree of autonominc dysfunction. I've seen it plenty of times with HIIT people that want to start doing running. They train multiple times a week. Look stressed and knackered. Think they are aerobically fit but can't run a 5km in less than 20 minutes and can't run a 10km at all.

I do HIIT all the time, e.g. 20x400m on the track with 3min walking recovery. But as you noted, one doesn't do these sessions to increase ability to exercise for a long duration, you do long runs e.g. 25km at aerobic threshold for that. I don't do these sessions to primarily target adaptions to my aerobic system either. Instead, I do HIIT sessions like 20x400m with varying levels of recovery to target different apations. E.g. with long recovery I can target anearobic capacity. With shorter recoveries and a lower amount of reps, I can improve lactate buffering and usage.

Finally, it's reasonably well known in athletics circles that if you improve your lcatate threshold, i.e. increase the intensity that you are able to stay sustainably aerobic, then you end up decreasing your anaerobic capcity. The reason why is that the lactate threshold training reduces your ability to produce lactate.

Source: I've been running a long time and have coached runners of various levels.
It's a separate interface where the output of the LLM is rated for safety, and anything unsafe opens a ticket to be acted upon by the medical professionals.
My guess is the Vision Pro was largely driven by a need to get real world data.

By giving it all the bells and whistles they get to find out about more things and keep it at such a price range that it avoids being viewed as a colossal consumer level failure (instead if it's known by the general public at all it's as a weird but impressive premium level failure)
I'll be curious what the collecter's market looks like for Apple Vision Pro a decade from now. I imagine there are far fewer of these things out in the world than Apple hoped there would be, and I wonder how that'd impact long-term scarcity.
Right, what they are doing is "make something useful with captured CO2" by using the CO2 to refresh the waste materials.
Isn't it part of the Apple way to release expensive and weird products at times to keep Apple in the minds of people as a luxury brand. Things like $400 wheels for Mac Pro or the $1000 stand for the external display.

I can see AVP as being half luxury and half tech-demo/devkit for a more budget friendly device.
Yes, let's make laws by passing laws.
> Everyone thought I was crazy for thinking this thing would get no traction. People want to spend less time plugged into screens, not less

Almost everyone I know (and people here on HN) thought this would be niche at $3500. But that doesn't mean people don't want to be plugged into screens. They totally are plugged into screens - just not Vision Pro.
Seems like a lot, yet isn't no even close to the speed needed to yeet something into space.
This fundamental issue seems to be totally lost on the LLM-heads.

I do not want additional uncertainty deep in the development cycle.

I can tolerate the uncertainty while I'm writing. That's where there is a good fit for these fuzzy LLMs. Anything past the cutting room floor and you are injecting uncertainty where it isn't tolerable.

I definitely do not want additional uncertainty in production. That's where the "large action model" and "computer use" and "autonomous agent" cases totally fall apart.

It's a mindless extension something like: "this product good for writing... let's let it write to prod!"
Migrating birds find refuge in pop-up habitats
RISC-V is currently slow compared to modern CPUs
They have produced their last batch for now. They are free to resume production if needed. From TFA:

>Apple will still be able to resume Vision Pro production if sales pick up since the production lines are not yet due to be dismantled.

If the item is still on Apple's website it's not discontinued.
at least in my circles it was considered way inferior to K&R. I read both and enjoyed both for totally different reasons.

But some Portuguese might remember "Samad" a mock person used in some of the examples. Which of course is "Damas" spelled backwards.

Relevant reddit comment: https://www.reddit.com/r/devpt/comments/qujip3/comment/hlmb9...
I think this describes very well what's happened.

I haven't moved my systems to IPv6, and have no current plans to do so, because it's a pretty major change (meaning a ton of hassle) that brings me no benefits that I care about.

If/when IPv6 becomes mandatory to connect to the internet, I'll go to the trouble of shifting my systems.
SpinLaunch: ~10000G

Rocket: ~5G

So roughly 3 orders of magnitude.
Apple products have been successful specifically because they attract the mass market right away.

Early adopters didn't use iPhones, they used HP iPaqs and Dell Axim PDAs running Windows Mobile. iPhones obsoleted them by simplifying the UI so anybody aged 8-80 could use it.

If an Apple product seems like it's for 'early adopters', it's already failed.
> Effectively, there's no real difference. The model is discontinued.

There is a huge difference. My interpretation is that the GP is making the point that with just the headline people will think the product as a whole was discontinued, not just this first version.
Without the bit of info that they are looking at how to make a cheaper one, some might take “discontinued” as a sign that they are giving up on the whole field. That’d be big news.

As to selling the rest of the inventory: of course they are free to sell whatever they want. But this is a device whose only real use is to be a sort of preview/testing ground for developers who want to get ahead on writing VR code. The pricing is ridiculous for a consumer device, and it is too goofy for Apple users to wear to coffee shops. Continuing to sell it without any note that it was pointless would be a massive betrayal to third party Apple devs if they aren’t planning on making a serious product.
Betting on Bali: My Journey into the Offshoring Business
I’m laying down a big bet on Bali! Let me share the evidence that has inspired me to take this leap. Maybe it will inspire you to jump in with me!
I work in this space. We manage thousands of e2e tests. The pain has never been in writing the tests. Frameworks like Playwright are great at the UX. And having code editors like Cursor makes it even easier to write the tests. Now, if I could show Cursor the browser, it would be even better, but that doesn’t work today since most multimodal models are too slow to understand screenshots.

It used to be that the frontend was very fragile. XVFB, Selenium, ChromeDriver, etc., used to be the cause of pain, but recently the frontend frameworks and browser automation have been solid. Headless Chrome hardly lets us down.

The biggest pain in e2e testing is that tests fail for reasons that are hard to understand and debug. This is a very, very difficult thing to automate and requires AGI-level intelligence to really build a system that can go read the logs of some random service deep in our service mesh to understand why an e2e test fails. When an e2e test flakes, in a lot of cases we ignore it. I have been in other orgs where this is the case too. I wish there was a system that would follow up and generate a report that says, “This e2e test failed because service XYZ had a null pointer exception in this line,” but that doesn’t exist today. In most of the companies I’ve been at, we had complex enough infra that the error message never makes it to the frontend so we can see it in the logs. OpenTelemetry and other tools are promising, but again, I’ve never seen good enough infra that puts that all together.

Writing tests is not a pain point worth buying a solution for, in my case.

My 2c. Hopefully it’s helpful and not too cynical.
Highest-Voltage Electron Gun
> The real battle should be whether we can host the software on machines of our choice, or not.

Evidently there is a market for those who want to run their own software and those who don’t care.

Apple caters to the latter. Meta seems to be taking the more open route.

Luckily pretty much all major VR platforms use OpenXR, so we have a better start than in the past.
Gov.uk transforms its search function with help from Google Cloud
Summary of article:

- Beginning: My custom auth works great for last 7 years, but looking for auth provider in new project so I don’t have to “roll my own auth”

- Actual reviews: These are all awful, broken and/or incomplete. Clerk is expensive.

- Conclusion: Use clerk if you can afford it
memset isn’t part of any abstract machine, yet compilers feel free to optimise that out, so we needed to add new functions that compilers wouldn’t touch.
It makes sense, it's just too expensive.

But I think they did this more to break into a new territory than to sell units. Of course, they didn't market it that way but that was probably their intention.

Next they're gonna come up with a cheaper device, hopefully below 2000 dollars with most of the things that made the vision pro interesting.
This is what we get when we allow the people with high compensation design the checks and the balances.
I’m perfectly fine with standing up to get and use anything. For me, the problem is that it’s a /headset/ and not something else - as they have a host of ergonomics and comfort issues, causes fatigue and headaches, closes me off from my environment (despite their pass through idea), etc.
You picked the best license, not a random one!
I think that the hope/dream here is to make end-to-end tests less flakey. It would be great to have navigation and assertions commands that are robust against simple changes in the app that aren't relevant to the test case.
The Power of Analogies: 7 Simple analogies explaining a Web3 protocol
The first list is basically what I said: they use licensed core designs and don’t make their own.

The second list is out of date. Intel has completely pulled out of ARM earlier this year and most of the others do not actually design their own ARM cores anymore. It’s become a lot less common in the ARMv8+ era.
I didn't see mentioned the size of payload compatible with this type of launch. I also didn't see anything about how loud it is, but I'd imagine it is quiet compared to a rocket launch. Would the payload be large enough to create a sonic boom on launch?

It's also just so much less dramatic visually compared to a rocket launch. It just feels anticlimactic. Still cool and interesting none-the-less.
Socialized medicine for Israel, nothing for Americans.

A bold plan. Let's see how the American people feel about this in 12 days.
I wouldn't go that far. But it is true that there are far many more possible outcomes because of how diverse the private insurance system is.

At the very least one guaranteed difference is that you would NOT not get a bill.

Then, a common scenario is a health insurance setup that covers 100% of the cost beyond a threshold, while the individual is responsible for the cost below that threshold.

My threshold is $6k for example. In the above scenario with the elbow, I estimate that the total cost would be around $100-200k. So I would end up paying the full $6k, and the insurance would take care of the rest.

The other common scenario is one where the threshold is much lower (e.g. $200) but the insurance covers e.g. 90% of the total cost. I find that option more risky, because I know the total costs can be staggeringly high, and 10% of a staggering number is usually also a staggering number :-)
That battery performance really surprising me. My T14 running debian averages ~5-6 hours of coding + browsing. Did you do anything fancy to get those sorts of results.
Televangelists complaining they need a third jet makes me wonder if it's just rationalizing after the fact. Or subconsciously some kind of flex.
I don't use magit, because I don't use Emacs.

But I've seen a magit power user, and arguably:

magit is the only git client I've seen that does some things better than CLI without being severely disempowered.

I only prefer the CLI over magit because I don't use Emacs. I'm not switching back to Emacs because of magit (or org-mode).

LSP is just too big for me, and Emacs has poor LSP, both in rendering, back-end performance, and effort setting it up.
Rather than halting VR/AR efforts, this seems to be just cutting production of the current model. That doesn't mean there won't be future models but it does imply demand was lower than expected.

We've had 10-15 years of companies trying to make VR (and AR more recently) happen. I just don't think it's ever going to happen.

People are led astray by books like Snow Crash but there are fundamental issues with both VR and AR. Latency is a huge one for both. AR fundamnetally has an issue producing true blacks.
SRAM also requires more power than DRAM and the simple regular structure of SRAM arrays compared to (other) logic makes it possible to get good yield rates through redundancy and error correction codes so you could have giant monolithic dies, but information can't exceed the speed of light in a medium. There just isn't enough time for the signals to propagate to get the latency you expect of a L3 cache out of gigabytes (in relative terms) far away big dies containing gigabytes of SRAM. Also moving that the data would to perform computations without caching would be terrible wasteful given how much energy is needed just to move the data. Instead you would probably end up with something closer to the computing memory concept to map computation to ALUs close to the data with an at least two tier network (on-die, inter-die) to support reductions.
Success of every modern attempt at VR hinges on limits of self-expression. Meta's torsoverse and Apple's extension of the office failed while Second Life continues on with a thriving virtual real estate and retail market and VRChat makes commercial deals to support a massive yearly furry convention.
> Everyone thought I was crazy for thinking this thing would get no traction.

I've yet to find someone who thought a $3500 headset would be a smash hit.
Yes, great point! We have an 'Assistant' feature where you can perform the flow on the device, and we automatically generate the test case as you navigate the app. As you mentioned, it’s a great starting point to quickly automate the functional flow. Afterwards, you can add more detailed assertions as needed. Technically we do this by using both the UI hierarchy from the app as well as vision models to generate the test prompt.
They need cameras for tracking your position and orientation. Also, tracking your eyes can be beneficial in many ways, i.e. enabling foveated rendering, not just for showing a blurred face on the external screen.
It was certainly named by some nerd: "(pushes glasses up) well, we only updated the quantized diffraction sorter, the 3.5 version number refers to iterations on both that and the field matrix array interpreter, so technically because the interpreter hasn't changed so we shouldn't upgrade the version". This engineer has never seen a dollar from a customer in their life.
The article mentions the law being proposed in Ontario requiring approval for putting in more bike lanes... but what about the strong mayor laws? If the city can just veto whatever comes from the province, does it matter?
Well, multiplication used to take variable time not long ago.

Anyway, IMO, CPU designers seem more aware of security implications than compiler developers. I expect more attention to those things in the future, not less.
Yeah it really feels like a devkit they sold in hopes someone would come up with the killer app because they hadn't figured it out themselves yet.

It's a shame as it seems like they maxed out the tech specs, but given the state of the art it still ends up being too low resolution for true MacOS productivity replacement, while also being too heavy & tethered to a short lived battery pack.

Maybe a worse-is-better version that is cheaper/lighter will sell more for entertainment uses.
Thanks for the well thought out reply here. I understand the solution you're proposing, but the thing is that it fails at the first hurdle.

> 1. Aggregate (in-memory or on cheap storage) events in the publisher application into batches.

Clickhouse's Tagline on their website is:

> Build real-time data products that scale

Except, the minute we start having to batch data to process it and stage it, we lose the "real time" part. If I'm shipping them to S3 to have clickhouse batch ingest them, I might as well be use Databricks, Snowflake, or just parquet-on-s3.
I wasn't prepared for an existential crisis this morning.
Write Satisfying Software: Is your code satisfying, or just beautiful?
There’s a LOT of conjecture in your comment.

Your very first line is one to begin with.

ARM also doesn’t seem to care if QC design their own cores. They just care that they renegotiate the royalty agreement. This is clear if you actually read their statements.
I don't know, IMO it would be better solved by profiles, environment specific settings (eg. settings.json + settings.windows.json), or override keys, eg:

{
"font": "xxx",
"[windows]": { // windows overrides
"font": xxx
}
}

I know using a full fledged programming language is infinitely more flexible, but I'm not sure a config needing infinite flexibility is a sign of good design.

If they want to stick with Lua I think they should allow both: write your config in JSON for the 99% of config that is easy, and allow to modify and return an updated config in Lua. TBH I just downloaded Wezterm a few minutes ago and got bored just wanting to add a Cmd+K shortcut to clear the buffer.
I can speak to even routine things like a childbirth still costing thousands of dollars with "good" insurance with a "low" out of pocket maximum and 100% coverage after the deductible.

It still cost 3 or 4 thousand dollars. So it's not necessarily those six figure costs that are tough to deal with but even routine hospital care that gets very expensive in the US. I'm fortunate that we can afford that cost. But for a lot of people even making the payments on that would be a hardship. We didn't even know it would cost that much even though we had called our insurance to try to figure it out. Nobody can tell you how much it will cost until you incur the cost which is absurd. And the hospital "price lists" are beyond useless.

It shouldn't cost anything to birth a child in a hospital setting like a birth center in any civilized country, and we shouldn't have to deal with billing issues and insurance companies in the insane first 12 weeks of a child's life when we're sleep deprived and just dealing with actual medical issues and adjustment. We've spent collectively hours on the phone with insurance for this and various other charges. The "private payer" "employer provided" system constantly produces bad experiences and outcomes for everyone. Every insurance provider I've had over the past 5 years is a company that constantly screws up and that I can't fire, unlike my car insurance.

The American healthcare system doesn't bankrupt us right away, but it does so slowly by bleeding us for costs we shouldn't have to pay and by robbing us of time right when we need it most.
IMO the right slicing for Google is hosted services versus client software. This "SaaS" segment has grown by bundling what should be two different markets, using the sticky network effects of the hosted services to prevent a competitive market for client software.
An AI related discussion board to help creators get found
I don't really agree that the title is misleading. I would fully expect the launched satellite to need its own engine and fuel (if nothing else, you'll need orbital corrections).

This seems to replace the booster stage, which is still a pretty huge deal, and is also the largest expenditure of fuel.

> Articles around SpinLaunch seem to be popping up lately which is a bit odd considering it's been ~2 years since they've done any testing and I've haven't seen any actual new announcements in these new articles yet.

No argument here. Their website also seems to be about a year out of date (their "in the news" stops in late 2023).
how do you want to detect if the user has a password manager? Checking if the DOM is changed by the password manager's autofill?
> Apple is free to continue selling what they have in inventory.

Remember the Apple Lisa. Get yours while their prices are low.
It's just a dream then.

It's completely at-odds with the strengths of LLMs (fuzzy associations, rough summaries, naive co-thinking).
I think part of the challenge Apple now has is convincing developers who were already on the fence that they should take the plunge now rather than wait for what looks to be a clearly superior form factor.

It’s not like customers (aside from those who already have the hardware) are beating down anyone’s door asking for the Vision Pro.

This is very handwavy, but if Apple does intend to pursue the glasses form factor it would probably benefit them to do the very make the very un-apple move of articulating how investments into developing for Vision Pro will extend into glasses.
what does it do though
why not plant trees then build wooden houses with them?
I would say that mobile apps are still the primary format for launching new consumer services, incl. new apps like ChatGPT and many others. However we’ve observed that teams are expected to do more with less—delivering high-quality products while ensuring compliance, often with the same or even smaller team sizes. This is why we focus on minimizing the engineering burden, particularly when it comes to repetitive tasks like regression testing, which can be especially painful to maintain in the mobile ecosystem due to use of third-party integrations (authentication, payments, etc.).