skysight-inc/HackerNews huggingface dataset:
When I first moved to New Zealand, I started a diary (before the term blog existed!) using PHP-Nuke. After a while, PHP-Nuke imploded and so I migrated to PostNuke. After a while it imploded so I migrated to Drupal. I had a choice at that stage between Drupal (version 4 it was) and Wordpress. Wordpress still had that "holes, billions of holes" stigma, so I went with Drupal.
Long story short, that's why my online diary (not linked anywhere) runs Drupal 10 to this day. It's now WAY overkill, but it still works well.
I've looked at moving it to Wordpress, or to some static generator but I've got over 3000 entries now and the migration never works very well.

I still find Drupal very easy to work with - my biggest gripe with it was when they just quietly started changing to not downloading .tar.gz but to using composer. And just assuming everyone knew what composer was and how it worked. In the end the friction it was causing me made me learn how to use it.

Anyway my point of this rambling post is that as a USER of Drupal - it's great. I don't write any code, but I can shuffle my website around as I please very easily, adding widgets, changing what's exposed both in the UI and RSS etc.

I didn't quite realise how uncool it was to still use Drupal until I read all these comments! :)
Roadrunner: Compact VTOL drone powered by twin thrust-vectored turbojet engines
If it had shown "eightwo" as the last part of a string, then people with overlap would fail the example because they'd be finding "eight" where "two" would be correct. Having it at the beginning means it was overlooked, at least for me.

Though, I have no problem with the "spec". This a code puzzle game, so figuring that out was part of the fun, in my opinion
These are the same idiots that said Twitter was days away from total collapse according to "sources familiar with matter" whatever that means.
I asked my last two hosts and both told me they had no problems what so ever with booking

Do you know what region/hotels are actually affected by this?
How science functions is how it functions. You do not have knowledge of the entirety of scientific endeavors, it only seems like you do, presumably due to being trained on propaganda, like an LLM.

Maybe you are conflating it with how it is supposed to, and is claimed to function by people who share the same form of faith based epistemology as you.
19 years here, and my terminal, editor, file manager and X window manager are all pure Ruby so as you can tell I love Ruby a lot, and frankly I love these changes - they've allowed me to reduce the size of my code in ways that makes it clearly more readable.

Nobody forces you to use them. I for one is extremely happy with most of the changes in recent years.
Drupal IS slow, but many "modern" sites in JS or Wordpress are pretty heavily cached too. There's just no beating "static HTML file served over CDN, with portions rehydrated".

Whether you generate that HTML in Drupal, Wordpress, or some other system, having to run code to generate it is always going to be slower than caching. Drupal is plenty fast for internal previews (i.e. when the server is not overloaded), but at the end of the day it's still a PHP app, and LAMP/LEMP is generally harder to scale up and across vs plain files.

And for what it's worth, a Drupal site cached behind Acquia/Pantheon/etc and their CDN can -- usually will -- be faster than an uncached JS site served from any single data center.
Where's the nuance in collective punishment of a population that's mostly under 15?

Where's the nuance in genocide?

Would you have said that Germany in the 30s was a nuanced situation?
Something I never quite realized – Johny Srouji's been at Apple for a while, even it looks like before the PA Semi acquisition. Keeping up with the chip industry is one thing; keeping up with the chip industry in an organization like Apple is another.

As a source of both continuity, and in terms of influence on Apple's long-term vision as a company, that's amazing.
I think the key point of the line you quoted was "for extended periods". Obviously flow states are useful, perhaps even required in some contexts, but to demand a full day of uninterrupted flow-state engineering bliss is IMO unrealistic and very often counterproductive. Software development at the company level is a team sport, and being actively hostile to necessary communication simply because it "interrupts your flow state" is the act of a prima donna or "rock star" developer. I've refactored a lot of code/been doing deep design work and been interrupted during said work. Did it make my personal task take substantially longer to complete due to the task-switching/getting my flow state back? Sure, but the interruption was for a good reason and my help was actually needed. On balance the interruption saved the company money and time because the drop in efficiency of execution for my slice of the pie was less impactful than what my help was needed for.

Now if you're getting constantly pinged for stupid shit that anyone could Google, then perhaps you should politely confront the person(s) doing so and make your expectations clear rather than declaring a pox on all interruptions.
Also letting legacy businesses die.

It is more often than not that family firms in particular collapse after one or two generations, if not propped up.
Advocating a better Kernel Integration for all
Without a doubt the best sort of press for Elon is this. Somewhere between “protest too much” and unabashed seething resentment.
>Hugh and his colleagues configured the PC and did a spot of training to ensure the AD was conversant with the modem he was provided

He was told which port to plug it in.
> I always wondered if it might have been because there were some legal risks...

What was in it for Sun to invest in GNUStep? Jobs was always resistant towards supporting other platforms. So it’s clear OpenStep was the last attempt at making use of the dying Next line.

I could maybe imagine a sales pitch scenario like “port your Mac apps to Solaris”. But when OSX came around, Cocoa was steered more towards the consumer market, not workstations.
> "it would be better if we never succeeded in the first place."

I don't see where anyone even implied that.
What is symfony, and why did it cause people to drop the platform?
In the article, Hugh is the IT person, not the Associate Director.
The people pushing RTO have to ignore a huge amount of data in order to make their point.
The article is behind a paywall but the picture shows that the Roadrunner is human-size, certainly not a gnat.
Websockets tracking in the browser can be weird. Try refreshing the page while you have WS selected in the Network tab
Your edited comment brings to light the concept of survivorship bias.

It’s important to recognize that there could have been farmers with superior skills and work ethic who, due to factors beyond their control like luck or chance events, still find themselves in poverty. To attribute financial success or failure solely to personal habits or skills is an oversimplification that ignores the multifaceted nature of wealth and poverty.
I think that muddies the water as much as saying that someone who supports UBI also must support foodstamps and housing vouchers. The point is pursuing greater _equality_. We are all heirs to a society that has produced enormous value; why should a small minority of kids get a huge extra unearned boost?

Purpose-constrained assistance is not _equal_ to inheritance, in that heirs to private wealth aren't generally subject to those constraints. Money that the recipient can choose how to spend gives greater freedom than assistance in that dollar amount. E.g. my understanding is a perennial issue with housing vouchers is that landlords often don't want to accept vouchers, so they are less effective than their face-value in dollars would be.
This is a much larger discussion, and it's not as easy as adding headings, subheadings, etc. to your comments. There has been a clear cultural shift against writing comments and properly documenting code. This is probably due to several factors, including unreasonable deadlines, bad architecture, job security, or meaningless output factors (e.g. lines of code).

This is why open-source code tends to be some of the best architected and documented code out there: it's pretty much the definition of "by committee" (in the best sense of that term) and meant to be inviting to anyone to contribute. So of course you want it to look nice.

At BigCo, these factors don't really come into play (even though it would probably be better for the company if they did). There's also a lot of differences between writing software and building robots. Systems engineers build and refine requirements documents, pages upon pages of "this tiny part should be built like this, should have these constraints, etc." with traceability, discussion, and clear deliverables. Software, on the other hand, is unfortunately mostly just "patch a few things together and get the login form working."
the Kissinger article in rolling stones got flagged as well, so anything that is critical of neocons apparently. The censorship everywhere is so fucking disgusting

https://news.ycombinator.com/item?id=38475482
On the topic of levels.fyi, the enshitification of the product has begun. It won't let you access things unless you provide your work email? Yeah right, like I am going to do that. A bunch of other mandatory questions in the sign up process also irk me a lot.
It’s not a sentiment it’s statistics. Look at the number of successful businesses that result in wealth creation.
Disclaimer: Head of Engineering, been working in startups only.

> In a startup, if you tell an engineer to do something and it turns out it's impossible

I see a problem with that approach.
To me, it's not about you telling the engineer what to do, they are not a tool to execute your bidding, they are a colleague with ideas how to achieve the goal you are striving for.

What is great about remote is that it kind of forces you to write down your ideas in some format, in PRs, in proposals, in documents. That gives the space and time for others to chime in, at their own pace, without your "body language" or your "room presence" shutting them down. Granted, it's not the American way with a top-down approach to startups, but if your working model is you simply tell your engineers what to do and they execute it, then imo you are missing 90% of their value.

> you will see him grimace and cuss you out in person, and you can adjust the plan accordingly....you won't get that body-language feedback

I have never had anyone at work "cuss me out", whether that's been remote or in the office. That sounds like a very unhealthy culture to me.

Additionally, I stipulate that looking for inscrutable clues in people's faces can instead be replaced with building a culture where you reward people for speaking (or writing down) their mind and all contributing towards the common goal, and there is a healthy amount of discussion (preferably written). As a technical manager, your role is to provide a clear goal to your teammates, and work with them to a good solution, not analyze their body language and making decisions based on that...

> yes while looking for other jobs and posting about how incompetent his manager is on Hacker News.

I'd be doing the same if my manager's main job is observing my every facial expression and I am not allowed to say no or at least explain why I don't think the task that's been presented to me is possible to be achieved in the proposed way.
Good point - thanks! Edited comment. Will leave this here to point out my failure.
Looks like auto-editing (of titles), e.g. "Thousands of People..." would be simplified to "People..."
Create your custom GPT for WhatsApp and Telegram in just a minute
You can now create your custom AI assistant to automate your sales, customer service, be your business coach or anything you want at gpt4sales.ai! Get a free trial or go pro with 15% OFF using GPTCUSTOM23
I would never feel comfortable interrupting people like that in an office. What if they’re in flow state?
How about just "sevenine"?
The methods that start with “call_” and “find_” are particularly redundant, because they aren’t any simpler than the code they contain. Technically true of all the methods given but the rest could be excused as explaining less readable syntax or for future expansion if parameters change. Modules should be deep, not shallow, is one design approach. This half fulfills that because the methods are private, but it’s also true that the method names are effectively comments yet they obscure the natural reading order for the code. See John Ousterhout’s A Philosophy of Software Design for more on this idea of deep vs shallow modules.

(Edit to add: another way of justifying the above service design pattern is to suggest that the code is DRY because you’ve extracted common sections to methods. This is taking DRY to an illogical extreme. You _should_ repeat yourself if your method calls are simple enough, and if you actually do need to repeat some logic in multiple places requiring a private method, you might find a better place to put it - for example, a filter method.)
I notice this pattern often appears as a result of taking rubocop’s default settings as gospel. It pretty much forces you into pointless abstraction by saying a method should be less than 5 lines, or a class less than 100, or whatever, even though such abstraction would offer no actual value.

Oftentimes when I suggest to change a rubocop default it leads to epic arguments as if you’re desecrating the bible. In fact, it’s just silly to not apply critical thinking to the quality of your toolchain, and that includes questioning the decisions of your linter’s maintainers.
I don't really understand what makes that better than something like (from e.g. Swift):

func double(x: Int) -> Int { x * 2 }

It just seems less readable because it's introducing not only an additional syntax for declaring functions, but also a secondary meaning for the "=" operator.

edit: in my original version of this comment I forgot to add the return type syntax, "-> Int", which Swift needs. I suppose eliding the return type is a bit more terse. You could also assign a closure in Swift to avoid that, like:

let double = { (x: Int) in x * 2 }

which is about as short as the Kotlin version, and has the advantage of not being "special" in any sense from any other Swift syntax (i.e., it's just assigning a standard closure to a variable).
> Because the only answer this ideology proposes is to "burn it all down and..."

Nothing wrong with that. Intellectual property proponents will "burn down" the entire technology field to get their way. Every day it's some new DRM bullshit. They couldn't care less about hacking and values like computing freedom. Then you have governments who want to do things like stop citizens from using strong cryptography.

The fact people currently get value from it doesn't justify its continued existence.

> succumbing to the chaos that you don't feel is important enough to control.

Controlling it requires destroying everything I care about. I'd sacrifice the entire copyright industry to keep it.

> I do appreciate you making that explicit though!

It's what I strived to do from the beginning. I want to see things clearly, as they are. If the conclusion is the current status quo is a lie and should be abolished, so be it.
Good lord. I can get a 2048x2048 upscaled output from a very complex ComfyUI workflow on a 4090 in 15 seconds. This includes three IPAdapter nodes, a sampling stage, a three-stage iterative latent upscaler, and multiple ControlNets. Macs are not close to competitive for inference yet.
Part 2 seemed fairly easy until I noticed "twone".

I used Rust and match_indices to get the answer.
That's very nice of you
I don’t disagree with any of these points, it’s just I’ve been involved in open science circles, where these things are always mentioned, and I just don’t see any material progress (maybe I’m not looking that closely though). I think the reason for the lack of progress is mainly funding—so until someone gets serious about funding (billionaires or taxpayers), it just seems like the same merry go around. It’s very expensive to replicate biomedical studies—but it’s the only thing that works. Maybe the tide is turning though and simply incentivizing/protecting grad students to become whistleblowers will do more good, but I fear this case was more the exception than the rule.
This is only going to become worse with further spread of USB-C; not even nerds and professionals can figure out WTF that USB-C port/cable carries.
You got it wrong. It is easier to start a business in the "socialist" scandinavian countries than it is in the US.

https://archive.doingbusiness.org/en/rankings
Maybe add to readme example of output? Either gif/mp4 with segment of animation?
Low interest rates decade made this pattern seemingly no longer hold, but I think we are getting right back to the old pattern for sure.

The next question is what to do about it. Wealth tax is controversial and hard to implement. It seems to me that simplifying the tax code such that capital gains and various forms of non-salary income didn't have preferential treatment would be an important first step. Further, an actual meaningful inheritance tax that isn't easily avoided by various trust schemes.
Pick apart everything that's wrong with the analogy you just made, and you might have your answer.
Yeah but I don't see that put forward nearly as much as all the camera tech they keep updating and promoting. I was just in Italy and they have building-sized promotional posters zoomed in on all the cameras at the back of the phone. Agreed it doesn't lend itself to advertising so much because it's less.. visual, but still I thought that was interesting.
> "As a matter of fact we should stop revering multi billionares. There definitely should be a comeback of the term stinkin rich."

I've always called 'em the "filthy rich" because you know that almost all of them what got that (financially) "rich", they all had'ta get way more'n just their hands "dirty".
The hallway pouncers are well known. I am remote but used to visit an office and knew to stay away from people who would do the hallway pounce and you’d walk away with a bunch of work. No thanks dude!
Location: San Francisco, CA
Remote: Remote/Onsite/Hybrid all OK
Willing to relocate: Yes
Technologies:
* AWS (SQS/SNS, Lambda, S3, EMR/Glue, Redshift/RDS, IAM/VPC, EC2, etc.), Terraform, GitHub Actions
* Python, Airflow, PostgreSQL
* TypeScript, Flask, D3.js, Pandas, PySpark, NumPy
Resume: https://drive.google.com/file/d/1uU5VtkJF3VBNoOGkKiCqD3wH3zl6NTtQ/view?usp=sharing
LinkedIn: https://www.linkedin.com/in/connerapeterson/
Email: capeterson@tuta.io

Hi! I'm Conner, I've worked across a variety of technologies, but generally focusing on backend, cloud infrastructure, system design, pipelines, data/platform engineering and visualization of data. I'm a bit of a generalist and interested in pretty much anything- if you are interested, feel free to reach out! I'd love to chat.
Location: KS, USA

Remote: preferred

Willing to relocate: no (can't afford to)

Technologies: (web) React/Node/Flavors of JS/MySQL/Postgres/Linux/AWS/PHP/Python/Rails

Résumé/CV: https://github.com/jdc-cunningham/jdc-cunningham/blob/master...

Email: my username at big G

I have about 5 years of experience, mostly in web application space. I tinker with hardware too, would like to go that route. I have no degrees.
> We are long past the point where most people are concerned about getting sick from COVID

Sadly true. I wish there was more discourse on HN about this. I don't think 10+ years from now this will be sustainable without revelatory therapeutics or vaccines that offer complete and total protection. It seems clear that this is going to be a slow burn where everyone's immune system gets nicked, little by little. Contracting covid once a year or couple of years seems to be the reality we're willing to live with and I am terrified of the long term implications of this.
Concepts.

What changes over time is syntax, but most of the concepts remain.

Source: 30+ year SysAdmin.
Innovative Method to Efficiently Harvest Low-Grade Heat for Energy
Agreed - having done a PhD in an experimental neuroscience lab, there's a nonsignificant number of things that nobody else in the world, even in my own lab, can do. I can train the techniques to others, and do, but this is separate from scientific discovery. There are no incentives for someone else to spend their time replicating my work using unbelievably challenging and expensive methods. It just wouldn't work in practice without a more fundamental restructuring of the whole enterprise (which is also necessary but hard).
The overall advice here (add comments to your code to delineate different 'sections" of a file) is ultimately a bad hack to deal with the fact that your codebase is not structured well into function / modules / classes with a single responsibility and the right level of composition. Refactor your codebase to put the related code together, and then this "problem" will disappear and your code will be much easier to change in the future
Yes, upgrades between major verions (especially to v8) were painful to the point where you seriously considered whether it would be faster to just start over from scratch.

Last time I looked at Drupal (a few years ago) the majority of Drupal 7 modules had not yet been ported to v8 which had been released for some time at that point.
What happens when the masses get fed up with the inequality and 400+ million guns in the U.S.?
Social Justice Environmentalism. Where's the dads in all of this. A better solution would be to build the houses on stilts.

“Stilt house”

https://en.wikipedia.org/wiki/Stilt_house
I think the SWEs can really take a lesson from the semi-technical sales people. World of difference even in a casual convo with them. I've been reforming myself too.
Glad to hear! How do your engineers deal with impromptu messages in Teams/Slack disrupting their deep work?
Teleport relicenses from Apache to AGPLv3
Spoken like a true type A personality. Lots of people don't need their ego fed constantly at the expense of others and are happy just being creative and thoughtful.
You're entitled to your own opinion of course, but your conclusions appear to be based on beginner-level misunderstandings. That doesn't seem like a constructive or productive way to conduct oneself through life.
Yeah, fair. I'm sure a lot of people don't want the OEM explosives and would rather tip it themselves.
Are you doing any extra work for the low latency? Or is it just those 3 API callouts (speech-to-text, text to response, response to voice) have gotten much faster on the third party side?
“Director of Strategy at Georgetown’s Center for Security and Emerging Technology”

https://www.theinformation.com/articles/openais-board-set-ba...
> Due to the historical averages of the rate of return on capital, he concluded empirically that wealth will continue to concentrate to the point to inheritors, to the extent that individuals become increasingly unable through labor to achieve parity to the inheritors.

You're obviously incredibly unlikely to become a billionaire.

If someone inherits billions - you're not going to out-labor them to become richer. Only luck will help there.

So where is the cutoff?

You can easily out-labor someone who inherits $2M at 50. >10% of people in the US amass >$1M (without counting their home equity) by around 50...

How many people are inheriting more than $2M? 0.5% of people?

You're never going to out-labor luck. It's always going to be better to be lucky than work hard. But luck doesn't scale, and hope isn't a great strategy.

I'm in favor of inheritance taxes. But this doesn't seem like the main driver of inequality....
Piketty's claim seems empirically obvious, but also virtually obvious to anyone who has created a gaming economy. The rich get richer faster than anyone can catch up, so you have to introduce artificial constraints like increasing prices for rich people.