skysight-inc/HackerNews huggingface dataset:
> Almost all police activity is there to document crime not to prevent it.

You say this like it's a bad thing (to the extent it's even true). One of the main purposes of the criminal justice system is to deter crime, and in order for the criminal justice system to work, someone has to be supplying the information.
I found the book Growing Object-Oriented Software Guided by Tests to be very inspiring. The book demonstrates how to evolve the code architecture, how and when to add new concepts and abstractions, how to listen to the tests, when to refactor etc. The tech in the examples is dated, but the gist of the book is very relevant.

Another classics are:
- Working effectively with legacy code
- Refactoring: Improving the Design of Existing Code

All of these books have a lot of depth to them
My theory is Apple bought Intel's timeline as much as anyone and Intel just didn't deliver.
>Real question: How long should she sit at her desk and twiddle her thumbs, waiting for your reply, before she moves on to emailing/phoning/interviewing a different candidate? Or perhaps she should pursue multiple candidates at the same time, to immensely speed up the process and reduce her time wasted just waiting to hear back from potential candidates who may never respond back?

Huh? Of course she should pursue multiple candidates at the same time. I can hold that belief and simultaneously express frustration with the above story. Do you think this is some sort of dichotomy?
You don't live in Arizona
Since it’s from 2021, does anybody has a follow-up on this? What happened to the researchers? Did something changed in the patch process to limit these attempts?
There are many reasons for having several commits in the same PR.

PRs often have a lot of overhead. They need a separate branch, CI jobs need to run, there are more notifications for everyone, separate approvals, etc.

Sometimes there's a need for keeping separate commits if they're all related to a single change. Proposing them all as part of the same PR helps maintaining that context while reviewing as well. Reviewers can always choose to focus on individual commits, and see the progression easily.

Sometimes it does makes sense to squash a PR if the work is part of the same change, but the golden rule of atomic commits always applies. Never just blindly squash PRs.

In fact, if the PR is messy and contains fixes and changes from the review, and the PR should have more than one commit, I go back and clean up the history by squashing each change to its appropriate commit. `git commit --fixup` helps with this, so I also prefer addressing comments locally rather than via GitHub's UI. Then it's a simple matter of running `git rebase --autosquash`.
I used Blot for about 5 years for Second Breakfast. Its ease of use got me started blogging. Very cool app/service, highly recommend.

I had it strung up with RSS to Mailchimp to auto-send new posts to a mailing list. Recently just switched to Ghost to make that more integrated, we'll see how it goes!
On the flip side I personally know a small business owner who got fined thousands by the feds for slightly overpaying his legal migrant workers. So failing to be properly exploitative is also illegal.
Starting a lifelong library on your first birthday
Additionally in certain circumstances it's less disruptive to use more water. E.g a nuclear power plant on a river: river water in, slightly warmer river water out w/o any or much steam generated. The more water 'used' the lower the temperature of hot water discharged, so kinder to the local ecosystem.
Bcash is not a slur. It is literally what the project is called by everybody except the bcash people trying to trick people into think it is related to bitcoin.
TFA is just a bunch of FUD. Non-commercial open source developers will be liable for nothing, and commercial software developers will be liable, and that liability will include their use of external open source, so what? Pretty much every bit of commercial software uses some external open source, and so what, using external open source does mean that one has to be able to deal with issues arising from that use. For example, even w/o liability if there's some bug in some external open source library that you use, you may have to spend time chasing it down and upgrading or contributing a fix, or locally patching the issue, etc. -- you used that external open source because it saved you time and money (but I repeat myself) and you took on some liability even before any jurisdictions might force you to take on even more liability. That's just normal. The calculus will almost certainly still be that using external open source is better and cheaper than writing your own bloat in-house, but you might need to do a bit more due diligence in picking better, safer external open source.

https://www.europarl.europa.eu/news/de/press-room/20231205IP...
Thank you, really appreciate this!
> Without the DMCA these things would just get built like Yubikeys with internal HSMs that require clean room practices to unlock.

There is always the Analog hole¹, and I don't think that can ever be resolved. You only need one A/D conversion where quality is paramount and after that you have DRM free copies.

> the media you like just stops getting produced at all.

This is a sacrifice I'd be willing to make if it means eliminating DRM and other schemes that do NOT promote the progress of science and the useful arts.

¹ https://en.m.wikipedia.org/wiki/Analog_hole
unrelated, but can every news site please build a lite version? This opened so fast and was so easy to read. I forgot how nice websites could be with HTML plus some mild CSS.
Media queries is the last reason I'm still using Sass, although I think the pendulum still has more room to swing in the compile-time direction for optimizations like de-duplication.
You are wading in dangerous territory. You are thinking too much. It might detract you from the notion that there is a simple solution to any problem.
Rebasing generally doesn't require repeated merge conflicts though? Since the formerly conflicting commit disappears and the non-conflicting one is now baked into a linear history.

Regardless, `git rerere` is supposed to solve that problem, but I don't do enough conflicting merges to be intimately familiar with it in practice.
Good news, my California town makes terracing so difficult to do that it might as well be illegal. So when it rains there's rapid runoff into a creek that makes a beeline for the ocean.
An up-to-date PulseAudio build for Windows with installer, service and sockets
CTRL+SHIFT+N New Folder/website

EDIt: this is a good thing.
Resistance to EVs?! They are pioneers!
Some people can’t stand the idea that they might need to protect themselves. They’re not anti-gun, when they have a problem they won’t call a social worker or priest to bring a book, they’ll call a cop to bring a gun. They’re anti-gun owner. Largely I think many of them resent being reliant in a way that other people have chosen not to be.
On my 2019 MBP, I found VSCode performance poor enough to be annoying on a regular basis, enough so that I would frequently defer restarting it or my machine to avoid the lengthy interruption. Doing basically anything significant would have the fans running full blast pretty much constantly.

On my M2 Max, all of that is ~fully resolved. There is still some slight lag, and I have to figure it’s just the Electron tax, but never enough to really bother me, certainly not enough to defer restarting anything. And I can count the times I’ve even heard the fans on one hand… and even so, never for more than a few seconds (though each time has been a little alarming, just because it’s now so rare).
Okay,so just as an example the very common penetration testing took Burp has no built in support for gRPC.
> They’re not afraid or contemptuous of individual foreigners.

For Japan, superficially, perhaps, because this would violate rules of decorum, but in reality, no, people are quite hostile to foreigners, especially non-Western foreigners. Being openly racist toward Chinese or Korean immigrants is considered perfectly acceptable. Discrimination in employment, access to housing, healthcare and service by businesses on the basis of country of origin is also common. Despite being technically illegal under the Japanese constitution, there is little to no protection of these rights, outside individual lawsuits.
The M3 Pro being nerfed has been parroted on the Internet since the announcement. Practically it’s a great choice. It’s much more efficient than the M2 Pro at slightly better performance. That’s what I am looking for in a laptop. I don’t really have a usecase for the memory bandwidth…
The CRA is not about liability or consumer compensation. The remedies for non-compliance are fines or removal of a product from the EU market. The forthcoming update of the Product Liability Directive, which will probably take a similar approach (exempting open source unless it is placed on the market, so as the article describes, developers of products that are placed on the market are responsible for the security of their products, including open source incorporated in said product) on the other hand is.

I only skimmed the OP and doubt it's intentionally confusing, but it is confusing because its prediction of doom is wacky. Manufacturers (eg developers of IoT devices, the insecurity of a major impetus for the legislation, apps, etc) will need to adopt modern development practices such as updating their dependencies when a vulnerability is known -- and that includes manufacturers that wrap a mostly open source codebase in a final product or monetise an open source codebase in various ways called out in the legislation.

Yes if a consumer is harmed by a completely open source thing not placed on the market, say something in Debian, they will not be able to sue the developers, and the developers aren't subject to fines etc under the CRA. That's the balance intended by the legislation (after lots of attempts to get it right), to not wreck incentives to develop open source, but to make product developers more responsible. In other words, the public policy is not exactly as you state it. :)
So it has a payback period of over 3 decades. Lots of talk of all the resources spent building it, only the carbon savings of usage. I wonder how long the carbon payback is. In an era of rapidly improving renewables, this doesn't seem like picking low-hanging fruit.
I mean at least on the West Coast of the US, my direct experience is that local farmers are selling at local grocers, that's where they sell most of their goods(that and to restaurants). Maybe not in Downtown SF or LA, but even in Davis or Sacramento for example, groceries are typically going to be locally sourced when they are in season.

This is because at the end of the day it benefits farmers and grocers to deal direct. Better produce, no middle man. Produce is very straight forward to sell by the pound too.
Could have rented that out
I've also taken David's compiler course, and it was excellent. I highly recommend taking any course he offers that interests you.
This app made me buy an iPad mini almost a decade ago
Browsing Reddit was glorious with this app.
Tourist visa is not meant for working?
For that matter, what if farmers had to pay a livable wage? Berry-picking is especially rife with social dumping.

It is a hot topic here in Scandinavia, because every season farmer will cry “no one wants to work!”, and then comes testimonies of indentured servitude at its worth, and sweat-shops at its best.

Many farmers here “import” Asian rice farmers to pick berries these days.
I really hope this stays top comment.
This is a great write-up and I love all the different ways they collected and analyzed data.

That said, it would have been much easier and more accurate to simply put each laptop side by side and run some timed compilations on the exact same scenarios: A full build, incremental build of a recent change set, incremental build impacting a module that must be rebuilt, and a couple more scenarios.

Or write a script that steps through the last 100 git commits, applies them incrementally, and does a timed incremental build to get a representation of incremental build times for actual code. It could be done in a day.

Collecting company-wide stats leaves the door open to significant biases. The first that comes to mind is that newer employees will have M3 laptops while the oldest employees will be on M1 laptops. While not a strict ordering, newer employees (with their new M3 laptops) are more likely to be working on smaller changes while the more tenured employees might be deeper in the code or working in more complicated areas, doing things that require longer build times.

This is just one example of how the sampling isn’t truly as random and representative as it may seem.

So cool analysis and fun to see the way they’ve used various tools to analyze the data, but due to inherent biases in the sample set (older employees have older laptops, notably) I think anyone looking to answer these questions should start with the simpler method of benchmarking recent commits on each laptop before they spend a lot of time architecting company-wide data collection
That‘s why I think „monolith“ should only apply to the deployment strategy.

Building an application with „monolithic deployment“ is way closer to the truth than „building a monolith“.
Many people who self-host email do so to avoid having years of all their personal email communications logs centralized at one third-party company with ether lax security or lax privacy.

It seems to me that you are proposing exactly this: routing all emails through one of these companies. How can this be a solution to "self-hosting"?
Most companies are cracking down on this kind of behaviour nowadays, in case you didn't get the memo.
I feel like this is too hard to just assume without actual calculations.

If it went to a grocery store, it would go from the farm to a central location (which is who knows how many hundreds of km away), to some distribution center (again, who knows how far away), to then go to a local supermarket. I wouldn’t be surprised if that’s less efficient than shipping it to a local market!

Aside from that, where do the products in a local supermarkt come from? Depending on your country, I’d be surprised if those bananas didn’t arrive on some freight ship. Talk about inefficiency! In my case, even tomatoes are often from a different country and then we export our own tomatoes to other countries too. It’s crazy.

Next to that, I’m not sure about the other points. At least in my country it’s cheaper (everything is in season), fresher and simply way better.

Regarding choice, it depends. I won’t find any locally grown bananas. But I will have more choice in vegetables and fruits that actually grow in my area. Personally I like that, since I care more about efficient and sustainable produce than shipping something halfway across the world for my pleasure.
If you genuinely don’t understand any of the perks of having a portable workstation, that’s one thing, but this comes across as a snide deliberate dismissal without even acknowledging them.
When I was a minor in the 80s and 90s, I had unskippable 30-60 second ads called commercials that targeted me during my cartoons (breakfast cereal and toys I could pester my parents to buy me) and, when I got older, MTV and magazines. Part of it was self selection (I started reading gaming magazines, so saw full page gaming ads). These publishers knew who I was through my subscription.

Sure, the segments were broader, but culture was homogenous by necessity. You didn’t see the cultural divergence of today that the internet (and targeting) have enabled.

I think the mechanics of targeting have changed, but we’re fooling ourselves if we think we haven’t had “targeted” ads for a long while before the internet took over.
Mastodon is amazing as it offers the same perks as mainstream social media but without all the privacy issues and big tech exploitation of users. But it still feels very detached from the real world. I use facebook or meetup to discover social events near me where I can find like minded people to talk to. There are so many things which I first learned from face to face meetings with real people. Things which I never would have discovered by simply browsing the web on my own. I wish the fediverse and the indie web would provide some simple safe decentralized means to connect real people in the real word the same way mainstream social media did.
That's interesting you saw less of an improvement in the M2 than we saw in this article.

I guess not that surprising given the different compilation toolchains though, especially as even with the Go toolchain you can see how specific specs lend themselves to different parts of the build process (such as the additional memory helping linker performance).

You're not the only one to comment that the M3 is weirdly capped for performance. Hopefully not something they'll continue into the M4+ models.
Brave. Seriously. Turn off a few things at first boot, it won't bother you after and is just nice and clean:

https://i.imgur.com/tuMGc3c.png
Well maybe not everyone, but most of us are born with some level of Novelty Seeking [0].

[0] https://en.wikipedia.org/wiki/Novelty_seeking
Setting the CPU flag after a comparison doesn't do anything useful yet, you also need to perform an addition with 1 or do nothing depending on the flag, and selecting between these two options is usually done with a conditional branch, unless the CPU can execute ALU instructions conditionally (ARM can do this, x86 only has conditional mov AFAIK).
> Squashing makes the diffs much more painful, such as by burying an important change in a sea of mechanical ones when they were originally in separate commits.

Can you give an example? I don't even think I understand what you're saying. You control your overall summary, so it's up to you to make it useful.

I would cite clarity as my reason for squashing! I think most people are just bad at organizing (& naming) their commits, so they make A LOT of vacuous ones, crowding out the forest for the trees. It's never helpful to see the git blame saying things like "Addressed PR comments" or "Resolved merge conflict", etc.

I do prefer a merge commit when the author has done a good job with their own commits, but that's rare. In all other cases, squashing is greatly preferable to me.
Just man tree if it's on your system. I used it for temporary jobs,
like where I needed to give some students a quick website of a folder
of source files. Not much to it.

-H baseHREF

Turn on HTML output, including HTTP references. Useful for ftp sites.
baseHREF gives the base ftp location when using HTML
output. That is, the local directory may be `/local/ftp/pub', but
it must be referenced as `ftp://hostname.organization.domain/pub'
(baseHREF should be `ftp://hostname.organization.domain').
Hint: don't use ANSI lines with this option, and don't give more
than one directory in the directory list. If you wish to use
colors via CSS style-sheet, use the -C option in addition to this
option to force color output.

-T title
Sets the title and H1 header string in HTML output mode.

and that's about it!
Or they just provide a really good service in the environment of ad-driven internet crap. I'm paying for it for the same reason as I pay for zerotier and give bcachefs donations - voting with my wallet for my environment to be a bit more like I wish it looked. And I'm happy to tell people about those things as long as they are better than alternatives.
Would good if posts youtube worked like twitter one where you got to see the channel name.. i absolutely hate mark rober and hope he fails and dissapears from youtube
It's also a liability thing. Keeping the legal attack surface minimal. It can result in you getting junk responses if you ask for feedback too. I've referred several friends to jobs who then got rejected, and they're almost always given the wrong reason when asking for feedback.

Especially if there's a perceived culture misfit or some manager thought we both would leave at the same time for a startup after a few months (this happened me more than once!) they all got insulted on their skillset instead by the recruiter. And sometimes even skills that weren't even in the job description!
You're a special kind of clown claiming that it is not economical white Apple profits are somewhere between 20% and 26%. They could build an update, they just prefer making more money.
fwiw, https://text.npr.org/ - https://old.reddit.com/r/news/new/
If water was priced appropriately it would incentivize hydroponics that captures and recirculates waste water to minimize usage.
My experience was similar: In real world compile times, the M1 Pro still hangs quite closely to the current laptop M2 and M3 models. Nothing as significant as the differences in this article.

I could depend on the language or project, but in head-to-head benchmarks of identical compile commands I didn’t see any differences this big.
> How do people with workflows that don't do any squashing do code review?

Going through the commits one-by-one or just looking at the entire diff both work just fine in most cases. In the former case, the commit messages (even if short one-liners) actually help understand the story of how and why the changes ended up taking the shape they did, so it's usually actually easier than just reading through one big diff.

> To me it always seems the main consideration deciding on commit size is about being considerate of the reviewer. Don't want to harass them with huge commits but also don't want to send barrages of tiny uncontextualized changes.

Commits should be atomic. Their size is irrelevant to that consideration. An atomic change may be one character, or twenty thousand lines (if those changes constitute an atomic (= singular and indivisible) change). This usually doesn't result in a barrage of tiny changes that are difficult to understand on their own, but even if it did, commit messages, the sequence of commits, the full diff of the MR/PR, as well as the attached information on the issue tracker you use (which you presumably have if you're doing code review) all provide more than enough context.
Let me tell you a secret: revenue from royalities is taxed as income.
I don't know about Koreans. But I don't think the Japanese "dislike" foreign cultures. They have a strong sense of and preference for their own culture.
please provide a link to all your software, so I can find bugs and then sue you for everything you have.
Thanks. Interesting resources I appreciate.
TFA seems to imply that under the proposed rules, none of that careful analysis will matter. A software "vendor" is liable and that's the end of the story. Microsoft or GNU foundation, doesn't matter

TFA might of course be wrong, but otherwise, my concerns stand I think.
Scala's immutable data structures, and especially the way they are used idiomatically and most obviously, have a lot of performance issues that are much bigger than the basic cost of persistent data structures. Namely, most commonly I will see developers default to pipelining strict operations like myList.map(...).filter(...).flatMap(...).collect(...).take(2) which forces/materializes the whole collection in memory for every operation. Better would be to first transform the list into a lazy view or iterator with myList.view or myList.iterator, and then do the pipeline.

They also lack the ability to perform multiple updates in a batch, except for some very limited cases. Other implementations like Clojure's support "transients" where you get access to mutate the data structure over and over again (as well as do reads), and then freeze the structure in place as a new persistent collection. JavaScript libraries like immer allow for the same thing. Scala's collections don't generally support this except in the form of "builders" which don't support reads and also don't support all the write access patterns (such as updating a vector at a specific index, or removing a key from a map/set, etc).
Trademarks that have conflict with common use words should have their vowels randomized: crovel, eppla, zonama, tema, etc.