skysight-inc/HackerNews huggingface dataset:
Once famous incident of this effect is reported by Oliver Sacks, where he confidently narrated a story that presumably happened to him during the war until his brother corrected him:

https://www.wired.com/2015/08/fully-immersive-mind-oliver-sa...
For rust, fibers (as a user-space, cooperative concurrency abstraction) would mandate a lot of design choices, such as whether stacks should be implemented using spaghetti stacks or require some sort of process-level memory mapping library, or even if they were just limited to a fixed size stack.

All three of these approaches would cause issues when interacting with code in another language with a different ABI. It can get really complicated, for example, when C code gets called from one fiber and wants to then resume another.

One of the benefits of async/await is the 'await' keyword itself. The explicit wait-points give you the ability to actually reason about the interactions of a concurrent program.

Yielding fibers are a bit like the 'goto' of the concurrency world - whenever you call a method, you don't know if as a side effect it may cause your processing to pause, and if when it continues the state of the world has changed. The need to be defensive when interfacing with the outside world means fibers tend to be better for tasks which run in isolation and communicate by completion.

Green threads, fibers and coroutines all share the same set of problems here, but really user space cooperative concurrency is just shuffling papers on a desk in terms of solving the hard parts of concurrency. Rust async/await leaves things more explicit, but as a result doesn't hide certain side effects other mechanisms do.
I use OTP Auth, it doesn’t get updated much but still maintained. I consider it « feature complete ».

https://apps.apple.com/fr/app/otp-auth/id659877384
> Whether you need to load your dataset from your hard drive, draw detections on an image or video, or count how many detections are in a zone. You can count on us!

I'm wondering of how useful pre-assembled programs like "draw detections on an image or video" are. There might be more here, but that's not a very compelling slogan. In my experience, these kinds of tasks only come up when you are demoing something like an object detector, or maybe for diagnostics, but in that case your diagnostics are highly specific to your task at hand. Dataset loaders are useful if you are creating a demo on public datasets, but in product work there is no pre-existing dataset. You're usually extracting the data yourself.

The API for creating polygon zones to filter detections looks nice, but that's a rather limited capability to warrant adopting a whole library. This looks like a toolkit for making computer vision demos, but not something I could see using to build a product. Usually, things like drawing bounding boxes on an image frame, or testing rectangle intersections are the easy stuff.

I do think there's a lot of room for reusable parts in CV, though. Of course the heavyweight in that space is OpenCV, but I wouldn't mind seeing a competitor that doesn't feel like a thinly wrapped C++ library in Python. The multi-view geometry space has few reliable tools in Python, and you spend a lot of time re-implementing classical formulas in NumPy, which I believe could be abstracted away with a 3D geometry toolkit. The kicker is that high-level, readable geometric abstractions (like lens distortion) always end up being a hot path in the code, and at some point they have to get replaced by specialized JIT-ed code.
There are only a finite number of possibilities here.

If you're stuck with a machine you don't like that shows you harmful advertising because it has no viable competitors, the problem is with the law, because it's propping up that institution or otherwise failing to enforce anti-trust laws.

If that machine exists, even though there are plenty of viable competitors that don't do that, and then you freely choose that one on purpose, it's not obvious that the company is doing anything wrong. You apparently like that kind of advertising.

The exception would be for some kind of information asymmetry, like the advertiser is lying to you and you don't find out until it's too late. In which case we're back to needing a law, in that case against false advertising.

Now I can tell why you're choosing this one, because it's a sticky one: What happens when they're lying about politics? We can't have the government enforcing a law against "lying" about political issues, because the very thing that makes them political is that people disagree and don't find the other side's evidence to be credible. We can't have whoever is in power at any given time censoring the opposition.

The solution we use for this is to put the determination in the hands of the public. The marketplace of ideas. If someone is full of crap, you prove them wrong in front of everybody, and then they lose credibility. This isn't perfect but it works pretty well in the absence of the aforementioned anti-trust problem. Because then instead of a handful of megasites that people get siloed into and fed content like livestock, you'd have a million blogs that intersect like the web. There would be no walls between sites, no way to prevent someone you're trying to mislead from hearing from the other side just because you're in with the site's operators, because none of the sites would be big enough to exercise that kind of power when the average person is getting their information from hundreds of separate sources instead of only one or two.

Sometimes companies have bad incentives. Those either get curbed by laws, or by free market competition, or... what's your alternative?
yep that's right. uses https://github.com/shashwatak/satellite-js.
I don't know why, but when I first read the title, I thought it was talking about a CVE in Halo: Combat Evolved. Made for an amusing error in reading.
Yep, I still open moreicons.dll everytime I need a fancy icon for a script shortcut
Mobile apps can be very profitable, I'm not sure where you're getting your numbers/info from. Profitable mobile apps are typically B2C which is challenging. B2B SaaS can be easier to sell, especially for one person and would typically be distributed as a web app. HN skews towards web developers so you'll typically get the feedback to go with a web app here.

I think it probably makes sense to find an interesting problem and validate it and then decide on how to distribute your software that solves that problem, while also considering what stack you're most productive in.
> So by your logic Rust introduced it so it could be "jammed down the throats" of all the dotnet devs..

You're missing his point. His point is that the most popular language, which has the most number of programmers forced the hand of Rust devs.

His point is not that the first language had this feature, it's that the most programmers used this feature, and that was due to the most popular programming language having this feature.
Except if we take humans as example, we do not "generalize from fuzzy to firm". We don't handle firm, we approximate it with fuzzy. Which is why formal logic makes for a fine family of puzzle games, but fares extremely badly at describing reality and reasoning about reality. Better suited mathematical frameworks are probabilistic in nature, and so happen to be fundamentally continuous.
Is Ruby on the decline? Is Ruby dying?
The best received interview question we used to give was for a role that involved fixing existing code bugs. The technique to design such a question: distill an actual problem your team faced recently into something a competent developer could solve in about 15 minutes.

The problem: we had a credit reset script that users complained about. Apparently it gave incorrect resets. We sanitized the db tables needed and introduced a couple more simple bugs in the data, sanitized the script and provided a couple different language adaptations with a couple added logic bugs.

The candidate was given access to the repo and it had a clean way to reset the tables. The candidate had 45 minutes to fix the issue in the associated bug report tickets.

We received so many compliments from candidates, even those who were not hired.

TL;DR: design a work sample test and give that. Base it on recent work. Give the candidate 3x the time to solve it than what it takes you or a midlevel dev on your team to solve.
Looks interesting and I'm going to try it out.

Curious about what differentiates it from something like pimsleur courses, other than price of course.
Fair enough. As others have noted the source code was leaked; I've got NT4, NT5, XP, XPSP1 and Server 2003 codebases to review from that, which I downloaded a good while ago. I've been a software developer primarily targeting Windows for 20 years, 10 of those professionally. I was a Microsoft MVP for half of those (2012-2016 inclusive). The reference to the date is found in the header of nt4\private\windows\shell\shelldll\unicode\format.c

The 32GB limit for FAT32 doesn't appear to be handled by the shell code or the dialog, so when I said it was handled internally to the formatting code, I couldn't actually find that. It's just somewhere loweer than the UI. What I did do howeever was boot up Windows 2000, the first version that did have FAT32, and there's no limitation in the format dialog itself. It goes through the entire process and then gives a "Volume too big" error after it has gone through the process, an error shared by not just the format dialog, but diskpart, disk management, and format, which certainly suggests that that is happening at some lower level. The dialog in question does just call into other functions to perform the actual format, but I wasn't able to find the actual source files for it.

>Dave for his part provided his credentials.

Now he understandably does leave out a bit of info about his history which you could arguably say is part of my "vendetta" that you observed. The reason for the proportion of comments is less a vendetta and more that I get kind of worked up every time stuff of his is posted and people applaud how great he is. He's no Dave Cutler but he certainly talks like he was.

Now, as to the tidbit. Dave Plummer ran a scam company that was sued by Washington State in 2006, "SoftwareOnline.com, Inc. ". He actually left Microsoft specifically to run this company. Court documents can be seen here:

https://www.atg.wa.gov/news/news-releases/attorney-general-s...

You can find David W. Plummer listed in the court complaint.

The short of it is that it was an online software scam company that tricked people into downloading fake Anti-virus and security software using online ads, and then the software delivered additional adware and nagware onto users machines.

That is why it may appear I have a vendetta. I don't trust a word he says and especially when what he says directly contradicts other sources. Mistakes in memory are one thing, but some of them are rather beyond the sort of thing I think is reasonable. Paired with his history, I'm convinced he's actually lying intentionally because he's trying to build a "following" and "Dave's Garage" is just his latest scam. That's why he keeps "coming forward" in posts and his youtube as writing this or doing that. What bothers me is that it's working, because most people don't seem to even question it, even where there are rather severe contradictions.
Notes on debugging HotSpot's JIT compilation (2023)
Yep, just a fan of the mission and have some friends on the team (and needed another statistic to fill out the bottom lol).
"customer trust is a priority to us"

Really? Well then someone is super crazy incompetent. You fired them already right? Whoever decided to do this in the first place, they're shitcanned for doing something so diametrically opposed to the companys priorities right?
I don't know what exactly "emergent" means in this context, but doesn't ice appear pretty rapidly? It appears between -1 and 1 degrees, and when cooling down from 100 to 75 to 50 to 25 water you would learn nothing about the freezing point.
cant find it on my iphone appstore
Okay, I'll have a go:

State is the data required to continue the operation of a program. That's always the case (also in non-FP contexts), but state is often smeared all over a program as only loosely and implicitly connected pieces whereas FP is mainly concerned with how to manage state (and thus also with how to compose such pieces of state into a greater whole so it's easier to manage).

Edit: Note that there is also "data you don't need for continuing the operation of the program", which we could categorize as "input", "output" and "wasted memory/storage/cpu cycles". The last of the three can obviously still be crucial for other reasons than program execution (e.g. debugging), which makes the line between output and waste blurry.
Yep, they should be.
Couldn't disagree more. In my experience, single-threaded event-loop driven async/await should be used for every possible concurrency need, with the complexity of multi-threaded concurrency being reserved for the rare cases it's needed. As auto-scaled services and FaaS began to become popular, I've found most any need for multithreaded programming almost wholly unnecessary.
Great suggestion. I'll add this as soon as I get the time. Being able to color code each shell would be super cool.
I put together a DIY solution, but I like my synology better.
> IMO the biggest reason to avoid threads is simply that it's ~impossible to write safe code using threads (e.g. without race conditions).

Javascript has race conditions too, even with no threads involved.
Warranty is irrelevant as the device is not a identical replacement and it did not fail, it operated as expected.
There were issues with Pinball on "Windows XP 64-bit Edition", or the Itanium version. A great video explaining this is https://youtube.com/watch?v=3EPTfOTC4Jw
Free Blockbuster - Leave Movies for Others to Borrow
You are mistaken in thinking that editors are supposed to vet submissions. That's not their job! Their job is only to weed out crackpot pseudoscience, which is a much easier task generally and also mostly solved by reputation, or papers outside of the journal's scope. And to edit the remaining papers into a constantly formatted journal publication. And that's done easy enough these days with LaTeX and online printing.

It is NOT the job of journal editors to rate or vet sincere submissions they receive that are on topic for their journal. This only started happening about half a century ago, when demand for publication started to significantly outstrip supply of journal pages, back when journals were actually printed on dead trees and had limited number of pages to keep costs down. The idea then was "we're getting 50 submissions but can only print 12, so let's rate them and pick the best ones." So they started the 'peer review' [sic] process to externalize that vetting cost. It largely didn't exist before then. Only now we can accept all 50, because why not? The marginal cost of one more PDF is practically nil.
It’s a fun site to look at!

Thanks for putting together the visualization.
I propose pillorying for lesser crimes and public executions for greater ones, but that’s likely not possible due to the eighth amendment. And suspending the constitutional would be the final nail in the coffin of the whole American project.

The modern western criminal justice system only really works when thieves and killers know what they are doing is wrong, but do it anyway. What you have in places like Pine Bluff is more like barbarians sacking Rome. They don’t think it’s wrong but do it anyway, they do it because they believe that it’s right. It’s an antique problem that calls for an antique solution.
Starlink.sx is really great and has a lot of data I haven't added yet. Working towards getting coverage hexagons + ground stations + more asap.
The stupidest thing to do first is moving platters. You move the PCB first from an OK drive to a NOT ok drive
It's not a technical mistake, it's a brilliant solution for when you need ultra-low-latency async code. The mistake is pushing it for the vast majority of use-cases where this isn't needed.
Another discussion where people don't get async/await, can't fathom why you would want a concurrency mechanism on a single thread and assume no one needs it.

UI programming, communication with the GPU, and cross runtime communication are good examples but I'm sure there are more.

Threads, green or otherwise, don't work for those cases but async/await does.
It would be so cool to have a tail.
Cool! I'd love to have a look at that, but the two links in the paper seem to be broken :( http://roadlessforest.eu/map.htm and http://www.map.ox.ac.uk/accessibility_to_cities/
Every volume of water IRL will disagree about the rapidity though, go below 0 and first it's water, then it has some ice, then more ice, and only after a while eventually it's all ice (and even then maybe it has some water underneath, who knows). I can't see how it is not common sense. But with LLMs the common sense was until now "they can't then they suddenly can"
So it's not magic then. A fs and a field in PATH means nothing unexpected happens.

So good then.
This might sound contradictory, but constraints are boosters for creativity.
Yes! This is a less practical but more funky version of isochrone maps.
Its not because of the tail but because of the farms. Sad state of how we do farming at scale.
You can check the code it generated in the long OP provided (this button is not very visible so I understand if you missed it).
GDPR solves exactly this, they are legally not allowed to sell this data in EU without explicit consent from you describing who to sell it to.
Async/await was invented for C#, another multithreaded language. It was not designed to work around a lack of true parallelism. It is instead designed to make it easier to interact with async IO without having to resort to manually managed thread pools. It basically codifies at the language level a very common pattern for writing concurrent code.

It is true though that async/await has a significant advantage compared to fibers that is related to single threaded code: it makes it very easy to add good concurrency support on a single thread, especially in languages which support both. In C#, it was particularly useful for executing concurrent operations from the single GUI thread of WPF or WinForms, or from parts of the app which interact with COM. This used the SingleThreadedExecutor, which schedules tasks on the current thread, so it's safe to run GUI updates or COM interactions from a Task, while also using any other async/await code, since tasks inherit their executor.
Not to mention, if water is pure and still enough, you can cool it below freezing point, and it still looks like a liquid, until it is disturbed and then it suddenly doesn't. Same with heating up above boiling point.
22 Tb is a lot of data. I wonder what people do with all the stuff they hoard?
auto is just type inference, doesn't change any visibility
Even without a warranty, this is something that a good legal system would make them liable for. It's not like it was sold as-is with a warning.

You think there's no obligation here?
Imagine going back to Susan Kare's shoes in 1983, having to design icons in black and white in only 32x32 pixels. Made even harder by the fact that people had never encountered icons on a screen before.

https://archive.org/details/paint.net-macintosh-icons
My biggest criticism of the task is that the article doesn't make the goals of the task - i.e. what the signals are that they're looking for - clear at the start. You can see in the comments that a lot of people have gone in looking for a kind of trick and made the whole thing more complicated than it needs to be.

I can imagine in the real interview, there'd be more build up to the task, and a description of what the interviewer was actually looking for. That way the interviewee understands what the purpose of the exercise is and doesn't end up lost down rabbit holes.

The more I think about this idea, the more it grows on me though, if you frame it well and find a task that can be explored in the given time frame.
In his defence he has clarified this was for the Alpha AXP 64bit build that had the problem https://devblogs.microsoft.com/oldnewthing/20220106-00/?p=10....
Sagrada Familia in Barcelona 'will be completed in 2026'
Heimdall "Magic Ball" Increases Transmission Line Capacity
Does it really matter?
I would say finding a problem to solve is the first step. From there you can assess if your target users are more prone to use a desktop website, a web app, or a native mobile app. I guess that some industries will only rely on installed native apps and frown upon browser web apps, and vice versa. Also, if your solution save people time, they would probably take the extra step of downloading something if they have to.
I work on a rather popular dev tool, and it's a desktop app. Nothing else would really make sense for what it does (maybe a web app, but it would be more limited in capabilities). But people are willing to download it because it's useful.

That being said, I think mobile apps come with different challenges regarding distribution, conversion, etc. Also, the learning curve is definitely steeper in my opinion. Learn the web techs (JS, HTML, CSS) and you will be able to build nearly anything you want, front-end (websites, web apps, hybrid mobile apps) and back-end.
If you have self encrypting disks you are screwed anyway and they are more common today than ever. There are some with the "nice" feature of resetting the initial key to the same value every time though.
Kuiper and other proposed LEO networks have a lot of catching up to do in terms of actually sending hardware to space.

There's a wikipedia page for list of starlink launches and just scrolling through it and skimming takes a considerable amount of time.

https://en.wikipedia.org/wiki/List_of_Starlink_and_Starshiel...
Oh yes, unfortunately, you can't do this perfectly. There are some graphs that cannot be embedded in Euclidean space in any number of dimensions, e.g. a 4-cycle with distance measured by path length. It's a good-enough approximation for visualization purposes, though.
> Also if implementing Mult was so straightforward that it can be done so thoroughly (including tests) in under three -hours by a single person that is opening the code base for the first time; Then why had this feature not been implemented already by then by the original project maintainers?

Exactly. That set off my warning bells too.
Not take from the beauty of these trees, but this time of the year is always my favourite time in Vancouver for the sheer amount of colour and pop that the city gets. Sometimes only for a few weeks only to be gone in the first storm and other times lingering for up to a month of beauty. Nature is fantastic.