skysight-inc/HackerNews huggingface dataset:
It's not even hype like we used to see in the build up to a big video game release.

It's just cargo culting and wishful thinking. People staring into the magic mirror, hoping it will clone their desires.

The phrase cargo culting or some meaningful equivalent should make a come back. Even after the 'great youtubening' of technical knowledge, it is easy to find people stuck in habituated imitation of tech skills and tech talk.

I love that people are interested, but cargo culting is no good water to drink from.
I'll second @viraptor and @hops answers : It is the same cause as the rise of microservices and DevOps adoption, easier politics. I worked for a big old company, and most of the problems were political and administrative. One big SQL database is quite efficient until the entity that owns it does not agree with the new CTO strategy and any another critical part of the business. Add an incident that shows the low resilience of the model and it quickly becomes a political headache, while the technical solution still seems evident to everyone.
Other than every single one that uses zigbee/zwave and not Wi-Fi. You can also use services like Cloud cutter or select devices listed on the Blakader website of tasmota-flashable silicon. Or if you're willing to go a little deeper into the weeds, you can use ESP home for more fine-grained control.
This, of course, isn't the only kind of conflict you can have. The delta on a feature branch will almost invariably be larger than the delta on a commit to trunk, and if everybody is merging feature branches, even if they are continuously rebased or merged with the trunk, they spend less time being tested in the final merged state and the risk of unexpected feature interactions (not textual conflicts in code) is higher.

Trunk based development is better because it forces smaller commits. Everything else flows from that. Smaller commits are easier to test, and have less risk of breaking stuff. Smaller commits are easier to roll back if they break stuff (fewer "unmerge" conflicts, i.e conflicts when you merge the inverse of the patch). Smaller commits force you to develop a better approach to schema and data migrations. Smaller commits force you to add support for feature flags, because a whole feature can't be implemented in a single easily reviewable commit, and now you have tech you can leverage for canaries and so on.
In git a branch is a name that points to a commit. When you commit to a branch, you create a new commit and then update the branch to point to the new commit.
State of Web Scraping 2023
Lets say what it is, there aren't enough African Americans in the white collar workplace.

Its not that we don't have Asians, Mexicans, or Indians. At least half the companies I worked for, white people were less than 50% of the workers.

Its not a current racism issue, its likely a relic of racism issue. A large number of African Americans grow up in poor areas, get terrible education, are among a non-work-ethic driven culture, and never make it to the American Dream. Repeat generation after generation. Sure there are racists from the south, but talk to an African American of privilege(middle/upper middle class) living in a city. They have little bad things to say, and mostly blame it on the individual.

The issue is the zip code. You can see it in how white people living in these same areas perform.
Facebook Messenger moved to a C++ server, built like the rest of Facebook C++ servers.

The story I heard was they were looking for people who already knew Erlang and were having trouble finding them, so they rewrote the thing in a language that they could hire for.

From my recollection, when I was at WhatsApp, we only hired two server engineers who had used Erlang before. I was considered knowledgable about Erlang, because I vaguely remembered seeing the Slashdot post when Ericsson open sourced it. Pretty much we hired smart people and gave them an Erlang book. As a result, I don't think we did OTP applications properly, and we might have missed out on a couple other things, and our code might not be very idiomatic always, but I think we did ok.

But, beyond hiring, Erlang is a weird fit inside Facebook's datacenter infrastructure. The Messenger server team was (and I believe still is) very small, and rewriting into something with less impedence mismatch for a small team to deal with probably made sense. For WhatsApp, we spent quite a lot of effort making our software fit at Facebook, and we had to give up FreeBSD and from what I've heard, hotloading, too.
There is no “ensuring” in life, only giving your best
It's always like that in consumer semiconductors. Intel has something like 3 to 5 actual silicon variants per generation that covers all dozen or two SKUs.
$25?

I live in a northern, Midwestern state and our coop (part of MISO) offered a one time $1500 and continued discounts (11%) per month on electricity for the capability to control utility curtailment (power control to the unit, no ability to adjust set-point or collect any other data). For winter it can only be in buildings that are non-primary living and can only shut off power to an electrical heating appliance (heat pump, boiler, etc). In the summer they can curtail your heat pump / AC for up to 15 minutes at a time.

I see the curtailment notification on my thermostat on hot days. But the house never gets warm. I have a newer heat pump that is rated up to 22 SEER2 and compared to my old on/off AC unit the variable speed unit makes a huge difference in performance, cost and noise levels. I never hear it running when it is and so during curtailment I don't notice it unless I see the notification.
American society aspires to be classless. Harvard wants its mini society to be classless, too. If it uses strictly objective, quantitative standards like SAT and GPA in its admissions process (in addition to legacy admissions), then it will have a mini-society that consists almost entirely of rich white and Asian kids. Since this looks like racism, they take the easy way out and use racial quotas to nudge the admission demographics in the right direction. Since this is literal racism, we find ourselves in today's situation: how do you untangle the societal damage done by enslaving a single race for hundreds of years?

The answer is that admission standards need to be changed to focus on the human qualities that schools are seeking in a way that is race-blind and does not give rich families a way to game the system. Doing so will be difficult, and there may be a few years of adjustment before they get it right, but it will get sorted out.
It's typical American usage where everything is awesome, amazing or exciting.

From my British view, without reference to a dictionary, awesome is when you hear fighter jets zoom overhead, or a metal band from in front of the stage, or Niagara Falls, or a mile-long freight train full of rocks shaking the ground as it passes. The target has strength, size and power.

An amazing thing is far beyond normal expectations in art, craft, or human behaviour. A detailed painting, where you step up closer and see it's even more detailed than you first thought. A carving from 3000 years ago with intricacy we didn't think possible at that time.

Something exciting causes strong, (mostly) positive emotions. A roller coaster ride, an impromptu water fight in the summer, stripping off clothes and running into the sea in a group, getting close to the end of a game with the realization that you might win.

Starting a job at Google and seeing 50 exabytes of data or a cluster of 10 million computers or whatever could be awesome.

Someone's clever and efficient algorithm that reduces runtime by 10× could be amazing.

Finishing the final university exam, expecting to pass the degree, could be exciting.

Changing from licence version 3 to licence version 4 is none of these. It might be satisfying, or perhaps rewarding for the people directly involved.
Affirmative action didn't apply to most universities, anyway. It was mostly universities that catered to the 1%.
• Hydrogen's end-to-end efficiency is low (losses in electrolysis + transport + fuel cell), so running costs are inherently a couple times higher than BEV's. This alone IMHO kills chances of mass adoption, as people will simply not want to pay more.

• EV charging stations are already common, unlike hydrogen fuel stations that barely exist anywhere. Charging stations are easier and cheaper to install and maintain (no need to deliver fuel or deal with moving parts for high pressure or cryogenic storage), so this is likely to stay in BEV's favor.

• You can't refill the high-pressure hydrogen just by plugging into your home outlet. For people who can charge BEV at home it is a huge convenience.

• The range of the Toyota Mirai is barely higher than long-range BEVs'. It doesn't even solve BEVs' main shortcoming, despite compromising a lot of space for hydrogen tanks!

• High-end BEVs can already recharge to 80% under 20 minutes, and don't require you to be near the car while charging (so you can get a coffee/toilet break at the same time). All of this trouble and cost to shave it down to a 5 minute refill, which you have to spend attending to the pump, is just not worth all of the fuel costs, wasted car space, and rollout of a new fuel pipeline.

Hydrogen may find uses in aviation, or long-distance trucks, maybe heavy machinery, but it's a poor fit for passenger cars and has already lost.
Training large language models with Intel Habana Gaudi-based DL1 EC2 instances
During the last 20 years, when we started to move away from big iron UNIX, only three distributions mattered to the projects I was involved with.

Red-Hat, Ubuntu and SuSE.

This will hardly change it.
Yes. It’s cool. But, it’s hardly revolutionary. They built a Siri that doesn’t suck.

It has the potential to be a Google killer as it’s much more effective at sussing out specific information. But, the ideological guard rails OpenAI insist upon are super annoying. You can never fully trust that you’re getting a non-politically biased output.
I'm Dennis, the creator of GreptimeCloud. GreptimeCloud is fully managed Prometheus backend solution based on Serverless DBaaS architecture.

We've been hard at work developing its key features:

1. Prometheus Compatibility: We've taken special care to ensure compatibility with Prometheus' remote read/write protocols. We built in PromQL support to ease your database interactions. Configure your GreptimeCloud instance as a remote write endpoint and you can store your metrics in a cloud database, though we're always aiming for simpler and more efficient methods.

2. GitOps Rule Management: Embracing the GitOps approach, we've enlisted git to handle Create, Read, Update, and Delete (CRUD) operations for your rules. This decision moves us towards stronger version control, better collaboration, and more transparency for developers, and yet, we know there's still so much more to learn and implement.

3. Built-in Visualization: At the heart of our Prometheus Workbench lies a dashboard builder, designed to lessen the complications associated with data visualizations. However, we're continually seeking ways to improve this. For those who desire customization beyond what we offer, our dashboards can be exported as Grafana JSON models for use in Grafana.

4. Pay as you go: In our commitment to optimising our service, we've improved our serverless DBaaS architecture, introducing 'capacity units'. This approach attempts to provide a fair way of measuring your database read/write operations. Still, we're always revisiting this system, aiming to provide you with the best possible experience.

We're humbly inviting you to share any feedback or insights about our platform. We truly value your perspectives and anticipate learning and improving our offerings based on your experiences.
Unfortunately that would mean doxxing myself. But its largely a somewhat complex CRUD app with a user dashboard. The stac is nextjs, tailwind, and nodejs, express on the backend.
I don’t think that “Where are you from?” has anything more in it than a conversation piece. Some people like traveling, you know, and share experiences. But I’m European myself, so dunno.

But the megaphones of anti-racism keep wielding the concept of race itself as a sword, they just think that since they are the good guys, nothing could possibly go wrong.

I don’t think there’s good physiognomics or bad physiognomics, is all. The whole thing is flawed. If you keep sitting on “race, race, race” all the time, no matter the intentions, instead of canning the whole concept as a harmful curiosity from the past which we don’t use anymore, you’re just going to promote it and get people to stay in the same freaking framework that enabled all sorts of crimes against humanity.
I got the impression back then that Ruby on Rails ate a lot of Perl's use cases. And the Perl 6 thing probably didn't help either. And it might have acquired a bad reputation due to the fact you can easily write really terrible code in it.
> I already have a master's thesis. This was harder. –
ais523

Expecting teams to do more than a master's for every desktop app?

You're not going to have businesses if you apply the standard of this post to everything. Respectfully, the attitude of "optimize the world and damn the consequences" feels like it usually comes from people who haven't tried to deal with the realities of making money with code, even at a level of just understanding why your manager is telling you that they're pushing the release forward against your suggestion.
No. It’s running on the same machine. Our goal is distributed ML/AI in line with our usual mechanism of running everything, everywhere. That is powerful because it means anything we build scales with our network.
Great point, perhaps “confabulation” is a better way of describing it, which means “the replacement of a gap in a person's memory by a falsification that they believe to be true”. For example, the term is sometime used to describe dementia patients, who might wander somewhere and forget how they got there. The patient then might confabulate a story about why they are there, e.g. they were getting their keys so they could drive to the store to run an errand, despite the fact they no longer have a car.
> whereas ~no-one working in tech believed that.

Company execs sure did. "Autonomous vehicles" is the mirage that Uber, Waymo and others dangled in front of investors and press for years. Can't blame the public for not figuring out that it was a fig leaf to paper over their eye-watering losses.
Dear Hacker News community,

I am thrilled to share some exciting news with all of you. After much delay, I proudly announce that I have taken the initiative to call not just one, but two separate repair services. One is to address the issue with my recently broken water heater, while the other is to finally fix the blinds that have been broken for over 18 months.

I'm sure many of you can relate to the frustration of dealing with household repairs that seem to linger indefinitely. Well, I have taken the proactive step of reaching out to professionals, and I am hopeful that these long-standing problems will soon be resolved.

Firstly, I have connected with a reputable repair service for the water heater. This essential home appliance will soon be restored to its full functionality, providing the comfort and convenience it once did.

Additionally, I have engaged with another repair service to tackle the issue with my broken blinds. These blinds, which have been a persistent eyesore for far too long, will finally be repaired, allowing me to control the amount of light entering my home and restoring a sense of privacy.

I wanted to share this news with the community because it signifies a small but meaningful personal achievement. It's a reminder that sometimes the smallest victories, like making those long-overdue repair calls, can bring a sense of satisfaction and relief.

Thank you for allowing me to share this update with you.

Best regards, Mordisquitos
That just sounds like a ridiculously narrow and specific subcategory of street/flâneur photography.
I'm extremely skeptical of the claim that engines killed mainstream interest in chess. The trend seems to only go back to 2004, which is not long enough.

My sense growing up in the 90s was that chess was a niche thing for nerds. I think it seems somewhat more mainstream now than it was then, while remaining fundamentally a niche thing for nerds :) But it seems very clear to me that it never underwent the broad collapse that I remember being broadly predicted after Kasparov vs Deep Blue.
Yeah, seems like something a professor said one day in class but never published.
Some people use long-lived branches in essentially the same way as short-lived branches function in TBD. Multiple sibling comments talk about merging in commits from main into their long-lived dev or QA branch multiple times a day, but this seems not really that different from just briefly branching from main when you need to do some work.
Six-year-old saves mum by calling for help on Alexa device
This—100%. The AI revolution with LLMs is creating a new type of interface with computers—the AI interface. Will it kill us all? Eh, probably not. Will it completely change human civilization forever? Eh... maybe not? (But also maybe).

But what it already has begun to do, and will continue to do is change the way we interact with computers. The era of having a personal voice assistant that is capable, adaptable, and intuitive is VERY close and that is something that's exciting. Siri and Alexa are going to look downright primitive compared to what we'll have in the next 2-5 years and that is going to be VERY mainstream, and VERY useful for huge swaths of the population.

Crypto still hasn't proven itself to be useful in any way shape or form that isn't immediately over-shadowed by a different medium.
It was impossible after we learned a few things:

-R0 was quite high

-Animals can hold and spread the virus, so even after vaccinations of humans it was going to be in the background

-not every country was trying for zero Covid, therefore at some point in the future if you ever hope to have an open border with a country that has open borders with that country, you get it eventually.

-there are no 100% secure borders
> This is also a bias which may take away from seeking diversity along other lines, such as class/upbringing, age, and being outside traditional recruiting networks for the job.

I'm glad you mentioned age. Age discrimination and lack of age diversity is a big problem in tech.

Whenever there's a discussion about underrepresented groups in tech, isn't it funny how older people are rarely considered?
I read that as "We don't want things to crash immediately when the data model changes. We want things to keep chugging along until the last possible moment, when we will realize we've been silently corrupting everything"
Subversion sucked for a lot of reasons. It had no good integration with code review (though there are some tools that can do it now). It didn't have a good way of doing a three-way merge, necessary for rebasing a change or porting it across branches (e.g. release branches for shrinkwrap patch updates, which was the style at the time), without additional tooling.

I wouldn't model how trunk-based development works based on experience with SVN.
It's a hermetic end to end test.

The ideal is to mock out the API with some sort of recording mode to autoupdate the mock.
Note that the URL needs a period on the end. HN strips it. I was very confused by the blank page with no history.
LMAO, this is where HN really loses me. I'm unable to understand how anyone could possibly think where anywhere close to achieving diversity of skin color. This is absolute insanity, and I'm expected to pretend this is a reasonable idea and debate against it.
You could have tested this easily. It doesn't look like you can get JSON directly out of it, nor any other type of data that meets the criteria of the query.

https://www.wolframalpha.com/input?i=Give+me+a+JSON+document...
If you're going to construct a weird strawman argument you have to at least attempt to reflect what is actually happening. It's easier to knock over when you conveniently fail to mention you and your neighbors are majority white and the mechanic still fits your family members into his schedule. And that most good mechanics in the city have the same situation.
Yeah, you're right. I just think that what the article argues for is a just a worse version of trunk-oriented git usage. Every benefit the article names is available via git, but git also gets me a place to share and automatically test my changes (which might be a simple but risky refactoring) without literally editing the trunk.

If there is a benefit to true trunk-based development over just trunk-oriented DVCSs usage, the article did not describe it.
Seems like a lot of confirmation bias on this thread, but I've found google search to be fine for most of the search queries I've used. The real threat seems to be chatGPT which has been a great timesaver for information that needs to be customized
>I prefer trunk-based development

I am devoted to fridge based development. Whenever I have something harder to solve, I open the fridge and eat something. That seems to help my thought process.
"Changing their focus to" vs "appointing themselves as an expert at" are two very different things.
you sound like an angry fastmail employee :)
you seem to have very special needs, why didnt you check out / test if what you want works before "migrating"?
it takes a lot of work to create services
it is cool if you are critical but your comments do not sound like proactive to me
I've never met a single person claiming it will cause mass unemployment in 6-12 months. But the impact of ~ChatGPT 10.0 in 5 or 10 years from now? It's a lot more believable given its current state. My anecdote is that everyone is concerned about what it will do in the future gives its current proof of concept.
Time in the office is not productivity. I work in the office 8:30am to 5:30pm daily. I often have days where I hit a point where going home, working out, doing a few chores, would all make me much more productive the next day. Instead I'm stuck sitting at desk until 5:30pm while my productivity drops off not just for the day but for the total week..

Usually the more productive my day is, the more ready I am to get out of there around 2:30pm or 3pm.

Work is best accomplished in strong stints with balance towards work & life. It's the difference between burning out in 2-3 years or staying in an org 5+ years.
There are some really good points here that are soured by an almost high-school-socialist level of rhetoric. Probably would've been better written as a continuous essay or treatise instead of a list. I'm sure, 24 years later, the authors would acknowledge that. But they can probably say the same in not so many words:

The Internet has enabled customers and employees to be far more informed and aware than ever before; companies trying to depersonalize and reduce will die, while those trying to personalize and communicate can win the loyalty of both.

I doubt publicly traded companies are even capable of this, and with the money printer constantly spinning, I'm sadly unsure they need to be.
"Pair programming", maybe?

Anyway, agreed. Particularly, I wonder how any significant refactoring is approached.
I was there during the transition. Even rewrote a site from perl to PHP.

For newbies, not having have to write the "magic" string,

print "Content-Type: text/html\n\n";

before being able to output anything probably felt quite friendlier and being able to mix HTML into the code, though it's not a good practice.

And the PHP standard library has quite a few things built in and combination of MySQL as LAMP was the hot word then, so I guess that's how it got traction and perl was gone from the web development.

I do like the Unix heritage of perl though. It does make you feel like a hacker when it feels the language has the shell syntax half baked in.
Zuckerberg’s Quest to Re-Enter China Faces Challenge: His Own Words
I think it can work for some teams and some products.