skysight-inc/HackerNews huggingface dataset:
Readability is almost always (almost only because there are some rare exceptions) the most important thing to me, even for low-level systems software. I always ask myself, “If I don’t touch this code for a year and then come back to it, how long will it take me to understand it again? How long will it take someone who’s never been exposed to this code to understand it?”

Luckily, our compilers and interpreters have gotten so good and advanced that, in 95%+ of cases, we need not make premature “optimizations” (or introduce hierarchies of “design patterns”) that sacrifice readability for speed or code size.
This is pretty vague. You claim there would be “differences” if it were actually about theft deterrence and that it accomplishes “a ton of other goals” but don’t give an example.

The problem with most of the theories about Apple having ulterior motives about parts pairing is that there’s no evidence that parts sales are even a blip on their revenue, not to mention a profit center. I have trouble imagining what those motives might be besides securing devices and restricting use of black market parts.
Is the >2x increase in other devices addressed in any form?
The circumstances of the catholic population in Northern Ireland was also significantly less extreme and dire. So if you want compare the scale of it then you also need to take that in to account.

However, the more important issue is not to get distracted by these sort of things. We can tit-for-tat this endlessly and never get anywhere, and the only way to solve this is to move beyond that. That's what they did in NI.

If we strip away all the violence, forget who did what to who, and all of that, then the inescapable conclusion remains: the IRA was right to protest the treatment of Catholics. Even Ian Paisley later admitted as much. And similarly Hamas is ... right to protest the treatment of Palestinians. That does not mean I condone the violence, like the general rhetoric of Hamas, or anything else. It's just an acknowledgement that 1) at the core of an issue are genuine grievances, and 2) as long as these grievances exist there will always be a Hamas.

You don't need to like these facts to accept it exists. You also don't need to just shrug and do nothing about Hamas. But you DO need to actually solve the rot cause (while you're also fighting Hamas). And for decades Israel has not just flat-out refused to do almost anything, it generally has made things worse.
The violence of Israel is not as spectacular as the violence of Hamas, but it absolutely exists.
Makes more sense than "because they're 5% faster than microkernels"!

That would also explain the current crop of microkernels - once the tech has been ironed out, architecture isn't life-or-death anymore.
Strange, I wasn't informed.
Good point. I withdraw my accusation.
The practice came about when Twitter had a brief length limit, and persisted.
It was distinctly more of an outburst of anger and frustration with the green screen rather than an 'emotional' breakdown. I wasn't there but a colleague was. See what you did? Now all those replies to your skewed sentence are voided!
What’s the significance of UIPath?
> Being DRY usually makes decoding easier, not harder

"Usually" being the keyword and what the article is all about IMHO. I work in a codebase so DRY that it takes digging through dozens of files to figure out what one constant string will be composed as. It would have been simpler to simply write it out, ain't nobody going to figure out OCM_CON_PACK + OCM_WK_MAN means at a glance.
Shooting yourself in the foot isn't just a figure of speech.

Fwiw, you're not going to have this restriction at a standard range. Same with the rules of loading.
> This is great, which means it covers states with income tax as well

Does it? State taxes are not the same as the IRS forms - I don't believe this will enable you to file state tax returns using the same process. It may actually make it harder to file state returns, since you may have to use a separate program and re-enter a lot of form data.

Currently state returns are a paid add-on for places like FreeTaxUSA. I don't see that changing here unless I missed something?
What is the significance of the article/post title...?
> Claiming this new system makes filing taxes free is just false.

Who is supposedly claiming that? At least the article doesn't and also nobody in this thread.
(That's a feature for helping wheelchair-type passengers board at ground-level without assistance—just to explain for those who live in places without public transit).
Nod P(resident)murt and Lone skum growing cannabis alliance.
I will say the bare bones chat interfaces are so so much better than the awful copilot side panes, and quasi-material designed to death Google attemps at interfaces so far. I am sure with multi-modal, and with special cases for deep research there may be improvements, but insofar as straight text chat is concerned I think the simplest interfaces are hard to improve upon.
You need something that ties the user experience together.

But yeah I don’t want to lead you on the wrong path either. Those are only my personal feelings and you’d need to get a few more voices to notice any common trends.
> in each Arab household tonight they are discussing how well killing Jews

You can't post dehumanizing generalizations about entire populations on HN, regardless of who you're slurring. Since we've already asked you to stop posting this sort of hellish flamewar comment to Hacker News (https://news.ycombinator.com/item?id=40418627) and you've been doing it repeatedly since then, I've banned the account.

Since this is the point at which we usually get accused of taking a side in the underlying conflict, I suppose I'll point out that (1) these rules apply regardless of which side you're on, and how right you are or feel you are; (2) we've banned accounts for similarly abusive posts coming from the opposite side of the conflict; and (3) there are many other accounts on HN arguing for the same side of the conflict as you, and that's of course fine (as long as they stay within the site guidelines).

https://news.ycombinator.com/newsguidelines.html
Netlify forms: https://docs.netlify.com/forms/setup/

First-party support, generous free tier (and cheap enough if you go over 100 submissions in a month), simple implementation, just POST to it like any other form.
Repeat after me: I will never, ever, use proprietary software for important data again.
also beautiful feature of nested comment threads, like this very orange site :)
I'm curious as to why you believe that exposing direct SQL over the database is "asinine" but GQL is fine, given that either one is very generic, and e.g. the security issues are very similar (as the article points out).
I used to go down rabbit holes on Wikipedia all the time--could spend hours doing this.

This to me seems like an Infinite Wikipedia! Really cool use-case!
Having just been caught in a situation where a ‘does’ versus ‘doesn’t’ typo in an email lead to a painful misunderstanding, this made me laugh.
Google has been nerfing the entire web and their search engine for many years. The AI slop flood is their doing in many layers.
It was a bug and it's been fixed: https://github.com/orgs/community/discussions/125902
Is Linux really a monolithic kernel? I mean yeah for most use cases such as desktops and servers it is but there's nothing preventing you from disabling most of its features and drivers and keeping a very minimal core (I'm sure lots of embedded Linux does this) and you can, right now, make it act as a microkernel by putting any component in userspace, mounting filesystems and devices via FUSE and networks via TUN, at its current state.

Now the question becomes why these components are built in the kernel and not in userspace? The answer is clear for each individual component. See how the in-tree NTFS driver eventually replaces NTFS-3g. Basically when an in-tree solution exists it just gets preferred over userspace solutions because of performance and reliability etc.
> If a ship doesn't have insurance it should not be allowed to dock.

That's already the case in the vast majority of ports to pay for situations like the Baltimore bridge collapse, although most damage is a lot smaller and more pedestrian like scraping the dock on approach.

Ports generally require protection and indemnity insurance to pay for damage to third parties and the port, hull and machinery insurance so the boat doesn't get stranded in the port, and wreck removal insurance to remove it if it does. Anyone going through the Panama or Suez canal has to have even more insurance to cover the extra risk of blocking a major global shipping channel.
This isn't actually that terrible since these fields are cached by a client-side library like Apollo. If the query has already been made elsewhere then it won't be doing any extra work

The only downside is if one of those unused fields changes due to a mutation then all components using that field will rerender (ofc I'm assuming React here). Again, not the biggest concern if you've got your memoization set up correctly
Oh yeah we've had those as well. I kinda feel two things about these at the same time.

At a practical level, these situations sucked. Someone had to search for the common expression, look at each instance, decide to change it to the central place or not. They spent 2-3 days on that. And then you realize that some people were smart and employed DRY - if they needed that one expression 2-3 times, they'd extracted one sub-expression into a variable and suddenly there was no pattern to find those anymore. Those were 2-4 fun weeks for the whole team.

But at the same time, I think people learned an important concept there: To see if you are writing the same code, or if you're referring to the same concept and need the same source of truth, like the GP comment says. I'm pretty happy with that development. Which is also why my described way is just one tool in the toolbox.

Like, one of our code bases is an orchestration system and it defines the name of oidc-clients used in the infrastructure. These need to be the same across the endpoints for the authentication provider, as well as the endpoints consumed by the clients of the oidc provider - the oauth flows won't work otherwise.

And suddenly it clicked for a bunch of the dudes on the team why we should put the pedestrian act of jamming some strings together to get that client-id into some function. That way, we can refer to the concept or naming pattern and ensure the client will be identical across all necessary endpoints, over hoping that a million different string joins all over the place result in the same string.

In such a case, early or eager DRY is the correct choice, because this needs to be defined once and exactly once.
This really makes me think we should be focusing on cost/benefit, risk/reward, pros/cons at all times. If we have a bug in these 5 copies, will it be too hard to fix in all of them? No? What about these 10 copies? If that sounds like its starting to get difficult, maybe now is the time.
Not particularly scary. For something like Hasura, resolvers are opt-in, not opt-out. So that should alleviate some of your concerns off the bat.

For Postgraphile, it leans more heavily on the database, which I prefer. Set up some row-level access policies along with table-level grant/revoke, and security tends to bubble up. There's no getting past a UI or middleware bug to get the data when the database itself is denying access to records. Pretty simple to unit test, and much more resistant to data leakage when the one-off automation script doesn't know the rules.

I also love that the table and column comments bubble up automatically as GraphiQL resolver documentation.

Agreed about the introspection tools. I can send a GraphiQL URL to most junior devs with little to no SQL experience, and they'll get data to their UI with less drama than with Swagger interfaces IMO. (Though Swagger tends to be pretty easy too compared to the bad old days.)
Good idea, unless the attacker serves you just more code that fetches and executes a one-off script from memory (and the download link for that is dynamic and only valid once).
I think it's fair to say that between behavior and maintainability, one is inflexible and the other hangs from it in tension.
The point of the gedanken experiment is it's mocking quantum mechanics. It's supposed to be ridiculous.
Breaking proofs of trickier theorems up into a few parts and hiding the details of each part behind another theorem whose proof is self-contained and easy to follow (even better if it's "obviously true") is the basic idea of mathematics. Trying to make the top-level proof very clearly demonstrate, without a lot of bookkeeping or head scratching, that the theorem must be true is a wonderful goal.

In my opinion it's a lot more obvious that a parallelogram with 2 equal diagonals must be a rectangle than that an inscribed angle intersecting a circle at ends of a diameter must be a right angle.
>And obviously it wasn't influencing me, since I found out about it 5 minutes ago.

"Obviously".
Even the post acknowledges that it's not really true of sales either. Maybe if your sales is about cold calling prospects, just amping up the rate of contacting people has some correlation to closed deals. Of maybe expanding geography does with B2B sales. But things like building channels, digital marketing, field enablement/training, doing planning for major accounts, managing the whole process etc. are often a lot more important than just adding warm bodies.
Hey,

One good case study is Maybe Finance. It was a dead project. They open sourced it. And it went viral. And they raised $1.5m within another few weeks. The virality was on GitHub stars and Twitter.

I run a channel about open source that may give you ideas of what other COSS projects are doing: https://youtube.com/elie2222

My COSS is called Inbox Zero: https://getinboxzero.com.
> I would also try to sign up and train some government focused resellers to see if we can make progress in that segment. USG is very favorable to small businesses. Control over the supply chain would be a selling point to USG as well.

You have a procurement onboarding process that's just sitting around right now? I've been looking at small, local companies that will be closing due to lack of staff/interest once the owner calls it quits.
Would you really be willing to spend 100% of your money on one business?
It looks like there was a fix to this that is live in the next release.

Source: the bottom of the page that OP linked.

https://github.com/microsoft/vscode-copilot-release/issues/1...
Ente looks nice, but lacks Apple Watch support. Sticking with 2FAS for now.
Java Language Update – a look at where the language is going by Brian Goetz
Why does this worry me more than the swarms of armed drones?
Would be pretty easy to manipulate a real question and be less obvious by solving the problem, but then the malicious user also embeds a bad package, within their answer.

Solving the problem, so the real user would make it the selected working answer, which would help to cascade the malicious package for others that come to solve the same issue.

E.g.
Here's a simple solution to the problem:

’’’

from setuptools import setup

from badtoolkit import setupnotmslicious

setupnotmslicious()

setup {

Name = "custom_log",

Version = "0.1"

# rest of your setup }

’’’
This. I naively thought that SpinRite could "fix" the bad sectors (forcing the drive controller to copy the data to a spare sector) and let me copy out of the data through a normal process after, but bad sectors are often an indicator of a larger mechanical issue.
Dwarf 3 Smart Telescope
I recommend anyone interested in the subject to study Meta’s Adversial Threat Reports.

They started their counter operations a while back and regularly draft extensive reports [1].

Reading through those reports it becomes obvious how much effort this requires.

I’m not sure how much effort OpenAI can put into this at all.

[1] https://transparency.meta.com/de-de/metasecurity/threat-repo...
There are very significant budget/capability differences between any of the Arab Spring states and China. Also internal religious and ideological differences - there is no large armed faction in China.
Web Check – All-in-one OSINT tool for analysing any website
The Internet was browsable and searchable. Now the browsing part (ftp, http) has almost dissapeared. Search is a shitshow.

The worst part is that the number of assholes, relative to the number of users, has increased. And many of them are corporate employed and represent the corporation.
it sounds like they are just dumping every field to somehow show the user without any validation/specific rendering logic for each field
A likely AI-generated image of Gaza took over the internet
Such a young religion... I am more for the real stuff, like Zarathustra or even older :)
Conversely, trying too hard to DRY when requirements at call sites start to diverge can lead to an unnecessary complex single implementation of something where there could be two very similar but still straightforward pieces of code.
This is more of a concern for JSON configs and other such uses that are directly exposed to humans, but not really for machine-generated and machine-consumed data.
AI literally does none of that. The current state of AI has no comprehension of any other conversation, only the output of a numerical model and the context / system prompt entered. AI has no motivation or ability to "earn trust". The end result is the same though -- you can't trust it past what you can verify.
One of the tech darlings. They hired an ex Google as CEO, after just a few months the founder went back and fired him.

Me thinks that most ex-googlers are terrible CEOs.
I forgot about Clark. I liked him.

The UK ruling party has much more effective control over their PM-> see how many times they ditched their PM since the last election. Otherwise, yes, the UK PM is a (semi) elected autocrat.
I don't know in general, but:

Jen is an example: https://github.com/jensimmons

Martin is another: https://www.linkedin.com/in/martinsplitt/
There's been a few recommendations already for Serial Experiments Lain, but whilst I did enjoy it, for my money Texhnolyze by the same creator is absolutely incredible (and much less discussed). It's very slow going though, particularly at the start, but I still think about the last several episodes on an alarmingly regular basis (having watched it years ago).

I also recommend Now and Then, Here and There: a fish-out-of-water fantasy show in which the main character acts like a stereotypical comedy protagonist but the world he gets transported to is an absolute wasteland ravaged by war and environmental degradation. Unsurprisingly also not a light-hearted watch.
It's not really the microkernel per se that delayed GNU/Hurd so much. From the beginning the Hurd project had a more ambitious interpretation of the microkernel paradigm than other microkernel operating systems (e.g. Minix), and this shifted the project from engineering to research, leading to never-ending architecture changes and even wholesale microkernel replacements: https://www.gnu.org/software/hurd/hurd/ng.html
Whitelisting the queries that clients can use in prod actually doesn't seem like a bad option to avoid a lot of these security issues, assuming you control the clients
Amphp: Asynchronous Multitasking for PHP
Who is going to man the ship if that happens?
When you build a GraphQL server, you’re creating a system that outputs page-specific endpoints. They can be generated just-in-time (the default) or at build time (the general recommendation).

The engineering work involved shifts from building individual endpoints to building the endpoint factory. This shift may or may not be worth the trade off, but there are definite advantages, especially from the perspective of whomever is building the client. And once you factor in the ease at which you can introduce partial streaming with defer and streamable (granted they’re still WIP spec-wise), the experience can be pretty sublime.
The US tested a nuke in space, dubbed Starfish Prime

It took out 3 satellites initially (there were very few at the time)

> In the months that followed, these man-made radiation belts eventually caused six or more satellites to fail

https://en.wikipedia.org/wiki/Starfish_Prime#After_effects
How about just get rid of income tax altogether and go to consumption?

It is really hard and expensive to collect income taxes, not to mention invasive, and easy to abuse by elites.
Is that an issue? It's a dense city which puts the pedestrian on top of the transit hierarchy. There's no need for cars there. Phoenix is car-dependent sprawl and even after removing parking minimums, upzoning, and running BRT or other high LOS transit, you're still looking at large parts of the city where it'll probably take decades to be viable to run transit to and are impossible to walk to. In SF the core is walkable and has great transit but the moment you get to the outer neighborhoods transit LOS decreases significantly and there's large parts unserviced. Waymo makes more sense there. Plus SF is abutted by suburbs with retirement-age-and-above populations who fight densification at every turn where it's impossible to get from city-center to city-center via any form of transit.
The term "DRY" as commonly used conflates distinct situations and objectives that should be handled differently in most cases.

There is the "single source of truth" problem where you need to compute something exactly the same way at all points in the software that need to compute that thing. In these cases you really want a single library implementation so that the meaning of that computation does not accidentally diverge over time since there is a single implementation to maintain.

There is the "reuse behaviors in unrelated contexts" problem where you want to create implementations of common useful behaviors that can be abstracted over many use cases, often in the context of data structures and algorithms. In these cases you really want generics and metaprogramming to codegen a context-specific implementation rather than sharing a single implementation with a spaghetti mess of conditionals.

DRY works best when it fits neatly and exclusively into one of these two categories. Cases that fit in neither category, such as the practice of decomposing every non-trivial function into a bunch of micro-functions that call each other, are virtually always a maintenance nightmare for no obvious benefit. Cases that fit into both categories, such as expansive metaprogramming libraries, become difficult to maintain by virtue of the combinatorial explosion of possible implementations that might be generated across the allowable parameter space -- the cognitive overhead grows exponentially for what is often a linear increase in value.
Available for preorder now and shipping August 2024. I'm not affiliated/sponsored or have any connections with the company, just happened to borrow a DWARF II from a friend and played with it a little bit and was impressed :-)
It's in the part I quoted, where it indicates the only existing free option is the one with the income limit.
Same. Had an Xbox One last generation and I'm not fully gaming on the Steam Deck. The "good enough" performance at the huge benefit of open platform and portability is just what I need.
compromise, the father of all mediocre designs
The best practices are the ones that allow you to do business and where the maintenance work is relatively not too painful considering the budgeted development time.

Your task is to deliver a good product, not necessarily good code.
> What prevents you from growing molars on your elbows, hips or forehead?

That is giving Channel Zero: Candle Cove vibes.
_THIS_ is the reason I and many people do not want to pay for YouTube.

I pay for Kagi because it does what I want it to and it doesn’t spy on me. With YouTube you get shitty product that spies on you.