skysight-inc/HackerNews huggingface dataset:
> This code could already be run in multiple threads today, with a GIL.

Yes.

> And it would be broken - in all the same ways it would be broken without a GIL, correct?

Yes, but the absence of the GIL would make race conditions more likely to happen.

> is your point that removing the GIL will cause people to take non-multithread code and run it in multiple threads without realizing that it is broken in that context?

Yes. They could run it in multiple threads with the GIL today, but as above, race conditions might not show up as often, so it might not be realized that the code is broken. But also, with the GIL there is the common perception that Python doesn't do multithreading well anyway, so it's less likely to be used for that. With the GIL removed, I suspect many people will want to use multithreading a lot more in Python to parallelize code, without fully realizing the implications.
Exploring the Limits of Transfer Learning with a Unified Transformer (2019)
Counter with selenium from fish.
Most things I write become almost obsolete in a few days
The $150 million had nothing to do with saving Apple. They had already secured a billion dollar line of credit and besides, the same quarter Apple spent $100 million to buy out PowerComputings Mac assets and license.

It was years before Apple became profitable and the $50 million was a drop in the bucket
Yep was hired once and hired someone once. Both great experiences, still friends with my ex-boss and my ex-coworker !
Although Molly may or may not believe that, this site doesn't seem to be capturing that thought. It is just interesting to see how different interest groups interact with the political sphere (reminding me that I should spend more time reading about such things - https://www.opensecrets.org/industries deserves a glance).
I don't know what you're asking for - this isn't some kind of controversial topic - any iterative algo that isn't polynomial time (or is approximate) is search.

In the context of compilers there are many. Look at this block diagram for Chaitin's register allocator:

https://en.wikipedia.org/wiki/Register_allocation#Principle_...

That's a search because it tries an allocation, possibly incurs a spill, tries again.
> how weird it is that you're fine with the government getting a record of all your phone activity

I don't like it, but accept it as the lesser evil. I'm from Europe and I believe the number of reported prevented terror attacks. The agencies need data access for that. Not good, but necessary.

But are you aware that Meta, Google, Apple, MS, etc. collect every kind of information about every user of Android, iPhone or WhatsApp, Insta, Facebook, Windows? Phone manufacturer, huge apps like TicToc as well. The kind and size of that data is crazy beyond imagination. I don't care if the government can get access to my WhatsApp messages when some of the most irresponsible companies, collect and use everything to their advantage. Are you really that naive and think that Meta doesn't analyse their gigantic data lake including billions of WhatsApp messages to predict the results of elections? That is the real danger to democracy.
All the solutions I found online seem pretty bulky and mostly used during surgery or for short-time monitoring. However, thanks to your comment, I found PetPace and I've already contacted them to see if their collar could help. Thanks a lot for your answer!
I'm saying that's the same thing. It's probably worse, actually, because imagine yourself at the head of a company the size of AT&T. What would you do -- what could you do? -- that would ensure that some random employee would never do something that makes you vulnerable to attack? How terrified would you be?

It's impossible to ensure what you're asking for. That's the problem with all of these kinds of rules, but worse, because at least something like SOC2 is providing a safe haven if you do the right things. Making companies "liable" for breaches is tantamount to saying that companies will never develop software again, because the risk is simply too great. Certainly, if I were in that kind of a situation, I'd rarely use a third-party service, and never use a startup, or a smaller company. I can't be responsible for the risks of AT&T, and every software company AT&T uses. That's crazy!

We're going to have to come to terms with the fact that "security" is a verb, not a noun, and that data leaks are going to happen, even in the best secured institutions. Punitive rules might improve security in the marginal case, but only at huge costs industry wide.
Setup/config is a necessary evil on any OS. It's part of the game that you must learn to be a productive coder.

If the setup portion is a huge issue, students can use a pre-configured web solution such as replit. There, you're guaranteed to become dependent on an opaque third party platform (all just to save some minor setup hassle).
You didn’t offer any evidence to back up your claim one way or another
For sure, whatever business endeavor you undertake, it's important to plan and execute effectively. I mention this aspect of the Pro AV services industry because someone I know started this way and quickly built a significant business supplying and managing video displays for events like Glastonbury, major acts like U2. This is a significant and growing market:

"The global event pro-av services market size was valued at $28.6 billion in 2021, and is projected to reach $56.9 billion by 2031, growing at a CAGR of 7.1% from 2022 to 2031."

https://www.alliedmarketresearch.com/event-pro-av-services-m...

Adding the creative VDJ sugar on to could be a good niche.
What else is on the list? That's interesting.
The more I've been doing open source maintenance and contributions where there isn't as much context between the code author and reviewer, the more I've been pushing for a little more than this.

- Add tests in a commit *before* the fix. They should pass, showing the behavior before your change. Then, the commit with your change will update the tests. The diff between these commits represents the change in behavior. This helps the author test their tests (I've written tests thinking they covered the relevant case but didn't), the reviewer to more precisely see the change in behavior and comment on it, and the wider community to understand what the PR description is about.

- Where reasonable, find ways to split code changes out of feature / fix commits into refactor commits. Reading a diff top-down doesn't tell you anything; you need to jump around a lot to see how the parts interact. By splitting it up, you can more quickly understand each piece and the series of commits tells a story of how the feature of fix came to be.

- Commits are atomic while PRs tell a story, as long as it doesn't get too big. Refactor are usually leading towards a goal and having them tied together with that goal helps to provide the context to understand it all. However, this has to be balanced with the fact that larger reviews mean more things are missed on each pass and its different things on each pass, causing a lot of "20 rounds of feedback in and I just noticed this major problem".

As an example of these is a recent PR of mine against Cargo: https://github.com/rust-lang/cargo/pull/14239

In particular, the refactors leading up to the final change made it so the actual fix was a one line change. It also linked out to the prior refactors that I split out into separate PRs to keep this one smaller.
I have a spare machine to do some offline work on running Haiku OS, the open source successor to BeOS. Even today it simultaneously feels 20 years ahead and 20 years behind.

Good example, the interface is incredibly snappy but no Wifi. I love the vision of BeOS but it probably would have been the death of Apple if they had gone with it.
Our metro only has Android support for transit cards because Apple want a cut.

Thankfully they haven't given in to stupid whining iPhone users and told them to complain to Apple.
A program that parses an arbitrary shelf label and then displays a large-print normalized representation (like the nutrition label) would be valuable.
A lot of engineers who use windows aren’t programmers. This is because a lot of custom engineering packages that require windows, especially since they were developed 20 years ago when windows was dominate.

But programmers have many more choices, and visual studio shops aren’t very common anymore, at least in the developed world, and I would bet countries like Russia and China as well.
I think owning foreign currency in NK is probably grey-market normalised at this point. However I imagine it's predominantly RMB and USD. The requirement that everything be done by foreigners in Euros is probably serving the purpose you state though. I suspect authorities might look the other way at foreign currency in general, or specific currencies like those I specified, but Euros might be taken as evidence of unauthorised contact with foreigners since there's no other good reason to take them.
> I repeat: Every rejected paper will eventually be published somewhere. Perhaps not in Nature, or Top Journal A, but it will appear in Respectable Journal B or Mediocre Journal C. And it will bare the seal of "peer reviewed".

I agree, but I dont know if it'a a bug or a feature. We had one paper that took a while to get published.

I prefer to use "peer reviewed and published in a good journal" where I'm not sure if "good" means A, B or C in your scale. But there are also D, E, F, G, ... depending on how finely you want to clasify the crap and predatory journals.

The problem is that outside my area, I really don't know which journals are good and which journals are bad. One of my criteria to not send the journal to the Z slot is if I recognize the publisher of the journal. Sometimes the impact index is useful, but it changes too much from area to area. I take a look at the other papers in the same jorunal. Too many single author papers or too many unrelated topics are red flags.

At the end of the day, for research or for posting angry comments in HN, the only solution is to RTFA. I read the abstract, skip the introduction that is usually too optimisitc, and go directlry to the tables and graphics. I learned that Ctrl+F "exclusions" is important in medicine, becuase I've seen weird methods to filter the patients.
If you want to get rid of scroll bars at least ensure any extra items are partially shown so it's obvious you can scroll up or down.
We don’t even have to adjust for inflation. I (well my parents) paid $4000 dollars for a Mac LCII with a //e card, a crappy 12 inch monitor, a LaserWriter LS printer, a 5-1/4 drive for the //e card and SoftPC. It had 10MB RAM
Form over function.

Every so often I use some old windows native gui apps and lament how clear the ui is and how fast they run
> The ubiquity of microcomputer BASIC in the 80s -- often as the first thing users see, or the only thing they see absent a cartridge or disk or something loaded into the machine to run something else -- seemed to suggest that computers are meant to be programmed, the way pens are meant to be written with. It was a complete accident, of course

I don't think it was an accident. BASIC was designed to be a simple language that was efficient with limited hardware resources, easy for beginners to learn and use, and powerful enough to do useful things. It turned out to be a perfect fit for microcomputers for those reasons. Especially in an era before platform standardization and giant software ecosystems, end-user programming was assumed and intended. (Even more so with "educational" microcomputers like the BBC Micro.)

> no one at the computer companies could think of what someone would want a microcomputer for, aside from video games

On mobile (and probably PC as well), games still dominate app sales by a large margin.

But in the early 1980s, microcomputer "business" (now "office" and "enterprise") software was already well established, including word processors (wordstar), spreadsheets (visicalc), databases (dbase) and software for mailing lists, billing, payroll, etc.
Airliner crashes would be as common as data breaches if regulators set the same expectations.
> Read through the published errata for modern CPUs

I totally agree, and this entire HN post is about the fact that these Intel CPUs probably have some yet-undiscovered erratas. Best theory at this point is that it's power/thermal related though.

> there will be a large number of combinations of instructions/actions that should be avoided

As a matter of fact, reading those erratas is part of my job, and no, it is very rare for such erratas to have the effect you're implying. Rare enough that this issue that is seen here would already have been matched against an errata.

I don't see anything in Intel's current errata — other than their in-progress responses to these reports — that could explain this. Here's the errata sheet for 13th/14th gen: https://edc.intel.com/content/www/us/en/design/products/plat... … do you see anything?
If one breach exposed all of their data, they don't practice the well-known security (since ancient times) technique of never having all your goodies in one location.
For a few reasons.

One, because actually building the lexer and parser from scratch is a useful exercise in a learning context, which is what this is.

Two, because the book wants to teach Pratt parsers, rather than LALR parsers. There’s a lot of literature out there on LALR parsers and generated parsers in general, but precious little on handrolled parsers. Covering material that hasn’t been covered to hell and back is a Good Thing.

Three, because lex and yacc generate C, and the book has two implementations of the interpreter, in C and Java. You could’ve used ANTLR to generate both parsers, but lex/yacc would only cater to the C version

And finally, because not everybody is on a POSIX system. Before WSL, using anything Unix-y on Windows was miserable. These days it’s mostly fine, but using WSL means you’re not actually building windows-native stuff anymore.
When the AI gets good enough to fly FPV drones with no datalink (which is sooner than you think) that will be the tipping point you are looking for.
I've been amazed at the silence about it.

I work in a firm very closely associated with CC and ACH processors, and I feel like the only time FedNow ever came up was when I mentioned it.

The low cost of acceptance and fast response times would seem to appeal to any merchant who's already begrudgingly accepting ACH, even if it's not a direct replacement for card payments.
But they weren't able to have a blue checkmark while impersonating celebrities.
I have a #leftoff tag in all my Logseq journals where I leave a description of where I was when I stepped away from a task. Use it everyday all day. Simple and works great.
I think that is, indeed, rather naive. Starbucks has an extremely efficient supply chain which ensures its raw ingredient costs are lower than what the small shop can negotiate, even moreso when delivery to the store is factored in. After raw wages, it can also offer health insurance and benefits to its employees at significantly lower per-employee costs than the small shop. It can often get a better deal on real estate, because landlords know that Starbucks adds prestige and enables them to raise rents on surrounding units. And of course, while mom & pop have to spend money advertising to the neighborhood with flyers, direct mail, coupons, etc, the Starbucks just posts that green mermaid logo and lots of people flock to it (and often are willing to pay more for the product).
Ooh, I’ve been looking for a good solution for this for years. Currently I use Parsec, but it’s closed source and not compatible with direct streaming from OBS etc. I’ll definitely check this out.
The technique of journaling as you work is sometimes called “interstitial journaling” and I became a big fan of it as a way to help focus as well as keeping track of what I was working on.

I made a tool to associate those notes with a color coded project and timestamp:

https://interstitch.app

It ended up being unintentionally similar to an invoicing time tracking tool a freelancer might use but the use case Im interested in is more personal productivity.

Can’t say the project has generated much interest outside my own personal use but I find it very nice to track notes as I go and then easily see how much time I spent on a given project. You can also add a #hashtag in the notes and then filter by that hashtag in the calendar view.

Completely free in case anyone else finds it helpful!
The third place is from 1989 book, The Great Good Place. Starbucks looks to have adopted it a while ago, at least 2008. But I have only heard it used by urbanists.
Like Firefox's Reader View for real life.
Oh yes, I agree with everything you said except on being able to test for being neurotypical. That's like expecting a test for being "not sick"/"not unhealthy"/"not physically abnormal". You can test for specific conditions or indicators and get negative results, but there's no test that can produce a positive result of "nothing wrong".
As far as I am aware, this saying is based on the reasoning behind C types rather than serious compiler considerations. In today's world such cpu-specific concerns are left to the compiler to figure out.

I'm sure you could contrive a language where this functionality is exposed, but I'm struggling to come with an example where this would be seriously beneficial across multiple platforms.

I strongly suspect that integrating editors of existing languages with tooling that informs programmers on how a given chunk of code performs with parallel execution units would be far more beneficial than inventing a language dedicated to such concerns at this time.
> Monero in the same time frame technically only experienced just over 1% inflation but from June to July this year is experiencing 12% inflation and then had nearly 19% deflation a few months back

That doesn't sound right; annual inflation in the Monero blockchain is order of magnitude 200k new coins / 18,000k coins total ~= 1% annual and dropping. it isn't really feasible to get 12% inflation over a month with fundamentals like that. So while it is volatile, the changes in price aren't being caused by inflation. It is just supply-demand fluctuations in a relatively niche asset. Inflation is the trend in value change caused by longer term changes in supply.
But there really was a time when famous researchers had blogs and updated them regularly with lengthy posts. Yes, there are a few people like Terence Tao who still keep it up, but the movement away from blogs a decade or so ago in favor of Twitter and the like is real, unfortunately.
Pretty sure the All In pod guys were using this company as an example of the AI bubble being over inflated.

"It's just three guys and a model and they think it's worth X hundred million"
Some good points to discuss here.

Firstly the git history managed via a controller / helm chart. That’s sufficiently complex. The mindset of k8s/cloudnative doesn’t translate easily from the pet vps control server which comes with its own disk and persistence. So conceptually a management layer like cooling is objectively easier.

But that’s a nit really.

I think the idea of management being time consuming is more interesting. It’s true. And I think it’s true no matter what you do.

Time consuming management applies to any sufficiently complex infrastructure or team. No matter what you have these questions to answer.

How is access ma aged?

How does debugging a broken build work?

How does secret and config management work?

How does disaster recovery work?

If you are storing config as code, how are you managing deployment of that?

If you use k8s, how do you manage feature deprecation across versions? Even a managed version won’t help you resolve having to move from some kind of resource/v1beta to resource/v1.

I don’t say this as a slam dunk against anything. I think there are different levels of comfort with certain paradigms depending on what you’ve been exposed to over your lifetime. And the solution that feels most convenient to you is what you’ll want to work with. And for each type of preference we are going to see different solutions. All of which will be time consuming to manage in their own ways at a sufficient level of complexity or scale. Basically I prefer talking in these terms because it shifts the conversation away from broad comparisons to something more tangible which is “where does the time complexity lie for this particular approach”. Teams can put that down on paper and decide which one is more palatable and then go with that.
Read Crafting Interpreters when building Crumb (https://github.com/liam-ilan/crumb). It was indispensable, especially the sections on scope and local variables. The balance between technical implementation and conceptual insights is super helpful, especially when trying to go off of the book’s set path.

It’s inspiring to see technical writing done like this. As an aspiring engineer, this sets a really high standard to aim for - excellent resource.
> Those customers are already untrusted, so it really does not matter.

Perhaps it doesn't matter to the health of your network, but if it leads to a customer's account being disabled due to incorrectly assigned abuse, surely it would matter to them.
Sure - pretty well every corporation you purchase a service from is required to store your credit card information as well. But there are stiff penalties from the government and credit card processors for unauthorized access to that information; consequently, it's rarely stolen.

Your address, cell metadata, phone number, email address, and passwords are leaked pretty well contsantly though.

It's not that corporations are incompetent. The laws and regulations mean it's not worth the cost to treat your personal information with any real respect.
They probably would still be the #1 phone manufacturer, still making terrible Symbian phones with terrible developer support. I was working for Nokia (and a shareholder) on their future phones c. 2004-2005 and it was horrible all the way down. Apple deserved to eat everyone's lunch.
The bodycam is a very interesting idea, but I need to find one that could possibly stream video instead of just storing it for later viewing. Adding this to my growing googling backlog :) Thanks a lot for the help!
If a company the size of AT&T finds themselves unable to move or do anything without creating security vulnerabilities, then it's time for the company to stagnate and go out of business, leaving fertile ground for more competent companies to replace them.

It would be kind of nice if companies would say "we've grown to our level of competence, we cannot safely do more, so we will keep doing the same, no more, no less, and make sure we do it well, and we will allow innovation to come from other companies". Instead, they say "let's recklessly chase every fad and who cares about poor security, it's not our liability".
If I could perhaps offer a middle of the road take.

I think there's immaturity on both sides of this. Many employees are treating employment as a kind of child-parent relationship, where as long as they're at least moderately obedient, they're entitled to be taken care of.

On the other hand, there's certain employers who feel a childish need to show how strong they are, by being ruthless, and making big dramatic "difficult" changes (not difficult for them) as a kind of theatrical performance of how action-taking they are.

If approached maturely, employers would be reticent to do layoffs like this, because they show comically poor staffing management, and cause huge waste and losses. And employees would put more effort into career defence, rather than putting all effort into working hard for an employer, who they can't guarantee will or can reciprocate their loyalty.

I.e. greater diligence is needed on both sides.
I'm working on a fitness app, I was mostly thinking about myself but as soon as I looked at best-selling fitness books it was clear that the market was pretty much all seniors. Although it could just be that seniors like books more, I also found similar trends in other media.