skysight-inc/HackerNews huggingface dataset:
Users think of Mastodon as analogous to Twitter. You can tell them they are wrong. But telling new and eager users they are wrong, and then offering an elaborate explanation as to why they are wrong and then requiring them to make a confusing choice with unclear consequences before they can even use the service is not a great strategy for growth.
> If you’re a Software Engineer/Developer, then consider that a service (at least, for me), is a piece of code running in a live production system, that YOU wrote, only YOU know how it works, thus YOU own.

I've grown unfond of this attitude. I most certainly don't own it. I have no IP rights to it at all. We're both being paid to solve different facets of the same problem. Coming at me with "this is your problem" isn't going to foster a collaborative environment with me. Which is much more pleasant than an adversarial environment.

Also: I'm not the only one that knows how it works, it's been peer reviewed in no small part to reduce my bus factor. All documentation requested is perfectly reasonable, and should be part of the organizations standard operating procedure.

If it's not part of the SOP, then no, you wont have those things. You need to work at a cultural level to change that, and for that you're much better off making allies than anything else. Make it clear how those things help you, and what you'll do to make the developers life easier when you don't need to worry about the basics. If altruism fails you, you can usually count on people to act in their own best interests.
Cyber Operations in Ukraine: Russia’s Unmet Expectations
"We want AI agents that can discover like we can, not which contain what we have discovered."

I wonder if we can even go beyond that and find ways to abstract "discoverability" so that AI agents can evolve into diverse species, perhaps entirely different from our specific ways of discovering. As an analogue, I think of the nervous system of octopuses, which is very different from ours, but capable of amazing feats.
I like significant indentation.

If you lose indentation, I want your code to break. It's a feature not a bug!

I'm not a big fan of Python, but significant indentation certainly doesn't seem to have hurt its adoption much...
I think we're talking on orthogonal lines. It's not companies who are competing, but workers who are competing with each other for jobs and being willing to take those jobs.

If the employment conditions are transparent and not unsafe physically (which is related to having full information about what you're signing up for), why is sick days something that shouldn't be open to negotiation or a person willing to agree to have more or fewer of them?

Suppose that a person is young and healthy and believes he/she doesn't need a lot of sick days. Why is it unreasonable for him/her to agree to a job that doesn't offer extra sick days? What's the logic / principle there?

Is it because sickness is unpredictable and an employee shouldn't have to suffer from something unexpected? Is it an information asymmetry argument?
Any image generator can do well in any two dimensional data, including SD, Dalle, Midjourney.

One feature of SD not discussed much in my opinion, is the deterministic key it provides to the user. This is what enables the smooth transition in every second of music it generates, and the next second in time. Moving the cursor of latent space between in a minimal way, creating the next piece of information and change it ever so slightly, it definitely sounds good to the human ears.
What would you call a 3rd one?
What issues do you have with BEAM?
My main problem with Mastodon is it's such a tiresome monoculture of opinion. So many people with the pretty much the same politics, biases, grievances as everyone else. Any server that dissents too much from this gets a fediverse block.

The whole thing is just so tedious. I don't know about the rest of you, but I enjoy reading opinions from people I have nothing in common with in terms of world view, and whom I vehemently disagree with.

On Twitter, you get that easily. On Mastodon, meh. Same old shit repeated everywhere. Boring and sanctimonious.
Have you looked into @scope?
I'm fairly confident that MIDI 2.0 is already dead. I really don't like to say that.

It was designed by a large industrial committee, in secret, with no transparency and no input from other interested parties. The opposite of MIDI 1.0. And it just stinks of it. It is overwrought by a long shot, with many bells and whistles nobody is asking for (there's a very specific, and frankly short, list of critical MIDI failings). It has no reference examples and will be awful to implement and to deploy over various transports. When it came out it went over like a lead balloon: nobody seems to want to implement it.
Wetter and warmer conditions probably also mean more forrest growth etc. Nothing is so simple.
You're making pretty extraordinary claims here.

While low carbon electricity might be the cheapest source of energy on spot markets, that's a really tiny part of the picture. We still need to figure out large scale storage and electrify everything, those aren't solved problems.

But let's assume we solve them. Do we have enough metallic resources on Earth that we can extract cheaply? Do we have enough cheap fossil fuels left to actually do that?

Historically there's no energy transition:

https://ourworldindata.org/grapher/global-energy-substitutio...

New sources of energy have made the world consume more of the old ones, not less. Same thing with technological innovation and gains in energy efficiency.
I use the bookmarklet they offer for saving for this reason. I wish addons had a finer grain permission system.
Continue to see parallel between elon and howard hughes.
Wow I love these pop sci articles, lists 4 genes:
- ESR1
- DRD2
- DCC
- TRAF3
that everyone has, and no details on what variants of said genese are actually relevant.
This is about as useful as saying "having a brain increases risks of suicidal thoughts". I need r-numbers and alleles to actually plug into promethase/23andme to see if any of this is relevant to me.
Gotta love how this one needed to be secret for so long:

https://www.archives.gov/files/research/jfk/releases/2022/10...

"In summary, and based on the above information, it is concluded that the letter was transmitted via normal Swedish postal channels. The letter is probably a "crank letter", most likely written by a Swede, using a Swedish-keyboard typewriter and Swedish stationary."
They are paying the COBRA. So this goes toward copays and hitting deductible. Assuming their health coverage is good (why wouldn't it be, it's a San Fran tech company?), this gets you pretty far.
There are in fact a few bars which might be called nightclubs.
Well, from the week of thanksgiving to NYE productivity is shit anyway. People are planning vacations, gift buying, visiting relatives/friends.

Doing layoff before that is beneficial for employer to save on labor cost (not paying low productivity time), and employee (allows better planning)
I didn't realize it did voice print. Either I missed that or they didn't have it way back when we first got ours.

But yes, something where you could trivially say "these commands are generic, these commands are not" and it works perfectly would be the thing that puts a household voice assistant over the top for me.
> Especially when promises and plans to use some of those windfalls of progress to help those harmed by it, seem never to see much follow-through.

The poor are economically better off than at almost any point in history; actual food poverty is almost unknown, objectively people are living in better houses than ever before, and so on. It just doesn't seem like any of that makes poor people any happier or poverty any less wretched, somehow.
I don't get why SRE is a job(and it was my title for years) The stuff listed is just good software engineering. If a swe cant figure out that they need to monitor their application (or really anything on this list) you have no business being anything other then a junior programmer.

These kinds of responsibilities create this weird scenario now where the team sre is the teams babysitter. Which just leads to the ops vs dev bullshit weve seen before. Toxic right off the bat.
Literally everything you're saying is wildly biased hyperbole or just outright unsubstantiated. I can't take this back and forth seriously if you're going to come it in such bad faith
So far, most of the responses are pretty underwhelming.

It's like that exercise middle school teachers sometimes do. They had out a worksheet where the directions tells the students to put their pencil down and do nothing. The rest of the worksheet is a series of questions or whatever.

80% of the students don't read the directions and start filling out the worksheet while the 20% who did read them are just sitting there.

That's what the feedback to an official CSS Working Group question has been like so far—people responding without having read the article; otherwise, they would know that…

1. Because of the way browsers work, the Sass syntax isn't an option—full stop.

The person who implemented Chromium's nesting support explains in the thread [1] why Sass's syntax is not an option. IMHO trying to revive a discussion about wanting the Sass syntax at this point is unproductive to say the least.

I've been using Sass and Stylus pretty much exclusively for a bunch of years—I get it. But that ship has sailed a long time ago, so let's not spend a lot of time on something that's not going to happen.

2. Perhaps before you respond, you should get up to speed on the issues at hand? There are links in the article you may want to read before you respond.

3. Here's what's arguably the most important thing to consider:

Which is best for the future of CSS? When people write CSS thirty years from
now — long after today’s habits and expectations are completely forgotten,
when future generations have never heard of Sass — which option will make writing
this language easy and elegant?

This requires thinking beyond your personal preferences or what you and your team have been doing for the past 10 years. It's about what's best the future of CSS for the long term.

We weren't writing Sass 20 years ago (Sass made its appearance in 2006) and we won't be writing Sass 20 years from now [2].

If you think about it, nesting is one of the top reasons why devs use Sass today; once CSS nesting is enabled in all three browser engines, a lot of devs won't feel the need to keep using Sass for every project.

I know there are other features and workflows that Sass/Less/Stylus enable but as far as authoring stylesheets goes, nesting is huge.

This isn't like the old days when it took years before you could use new CSS in production—Chrome already has an implementation (I've used it) and once there's agreement on the syntax, I can't see why Apple, Google and Mozilla wouldn't be able to ship it Q1 2023.

So think about what's best for CSS and the web based on where things are headed—this isn't about you. Okay, it's not entirely about you and your team; but it's mostly about us— current and future web developers.

We're going to need to live with this choice for many years to come.

Let's not screw this up.

[1]: https://news.ycombinator.com/item?id=34007053

[2]: To be pedantic for a second (this is Hacker News after all ;-)), yes, someone will have to work on some legacy codebase 20 years from now that has thousands of lines of Sass… I get that. But we're getting close to a point in time where the vast majority of new web projects will not need to use Sass.
Personally I'd never click on your proposed title as I have 0 interest in Scala, but I clicked on this one and was pleasantly surprised by interesting story. Making everything sound robotic is not the way.
This questionnaire is kind of foreign to me since I see an SRE's job, more or less, as defining interfaces and then forcing everything to adhere to them (politically or manually).

These are the questions I find useful:

"How is capacity for the service allocated right now?"
"How is software updated right now?"
"How was the last outage handled in as much detail as possible?"

From there, just about everything answers itself with a couple days of reading code and poking at machines, particularly from the output of `lsof` (log files, config files, what the service talks to).

Half of these questions could be answered with grep and once you get proficient at grep, you can answer questions faster, and more importantly, more accurately than the people who work on the services themselves.

> that YOU wrote, only YOU know how it works, thus YOU own.

I find this attitude pretty toxic. If you are in an SRE vs Product Dev mindset, then you have bigger battles to fight than service manipulation.
Getting covid once right after sleeping in same space with all vaccinated. Positive - stayed at home - pretended to be ill. Friend, vaccinated, panicking getting covid after vacc..
Buut..this is Divide and Conquer, don't you see?
I am a fan.

Been using it for several months now and it’s my default reading location and I read a lot. Reading is essential to my life and work and I have been looking for a solution that solves all my information consumption problems. Readwise has a good chance to be that solution as long as they don’t go the way of Google or Evernote.

One continuing irritation: PDF reading on iPadOS isn’t as good as dedicated apps (I use PDF Expert). Highlighting works fine, but writing by hand using the Pencil is nowhere near as responsive or accurate as PDF Expert. I hope you invest resources into making PDF consumption the best in class - it’s the only thing preventing me from fiully embracing Reader as a complete solution.

A suggestion - not arising from irritation, but a matter of positioning - much of the communication of Readwise/Reader’s utility is around productivity, of reading to optimize information uptake or insight maximization. I would prefer if it also highlighted creativity and imagination. I read to make new connnections and (hopefully) think new thoughts that I haven’t thought before. It’s an idyllic vision of the vocation of reading but one that has a long history in the annals of bibliophilia. Perhaps you should target not just the Tech Bro, but also the Romantic Reader.

PS: an unexpected delight - I liked how I was onboarded by an existing user and had to turn around a couple of weeks later and help onboard the next generation. If done well, Readwise/Reader can become an essential social reading app for nerds, with the tool being the hub for a community of serious readers. Books are already read in circles - perhaps you should try to replace Google+ as well as Google Reader
How about a new file extension. .css2 or.xcss or something?
Confirmed. The last snapshot in the Wayback Machine shows that they tweeted a link to @ElonJet on Mastodon before being suspended: http://web.archive.org/web/20221215173935/https://twitter.co...

Part of me wonders if this was an intentional 4D chess move on Mastodon’s part to make it look like Elon is silencing competitors and get more attention in the process.
> The same website that makes a strong promotion against ad tracking: https://lichess.org/ads

What does this have to do with clickbait?
Came here to say this. What a tease.
My favorite recent Amazon search: looking at LCD displays, one was categorized as “Style: Women’s”

Was this a classic case of review laundering, where a blouse was replaced with a computer monitor? Or did some code somewhere overlap with attributes that normally apply to clothing?

Whatever it was, the categories and filters on that site continue to degrade.
It’s definitely common in parts of the world where workers have organized to have severance required by law or through other organized means. When workers demand it one on one with their employers, they have no leverage and are at the mercy of “nice owners” (ones that value reputations effects created by worker-favorable market conditions)
consolidating whole ecosystem under their own hands. hope it's going to be beneficial for ros. also now they seem to own both mujoco (deepmind) and gazebo (ros) after this deal
Employers are by dollar amount the biggest actual thieves by far in the US. Business owners ought to generally receive more scorn and critical evaluation than common property thieves who represent a thin fragment, if we really care about theft
> Basic income or revolution. That's going to be our choice.

I fear you are right. But neither of those is going to be an easy transition, if only because the effects of all this innovation is felt disproportionally by people in countries where such a revolution will not do anything to give solace.

Basic income assumes that the funds to do this are available and revolution assumes that the powers that be are the parties that are in the way of a more equitable division of the spoils. Neither of those are necessarily true for all locations affected.
Basic income or revolution. That's going to be our choice.

Evolution.

We have such vast wealth and our historic methods for trying to make sure most people are taken care of are failing us. Those methods were rooted in the nuclear family with a head of household earning most of the money and jobs designed with an assumption that he had a full-time homemaker wife buying the groceries, cooking the meals etc so he could focus on his job.

We need jobs to evolve. In the US at least, we need to move away from tying all benefits (such as medical benefits and retirement) to a primary earner. We need to make it possible to live a comfortable life without a vehicle. We need to make it possible for small households to find small homes that make sense for them, both financially and in terms of lifestyle.

There is a lot we can do to make this not a disaster and make it possible for some people to survive on very little while while pursuing their bliss so that we stop this trend of pitting The Haves against The Have Nots and make the current Have Nots a group that has real hope of creating their own brilliant tech or such someday while not being utterly miserable if they aren't currently wealthy.
typo on the landing page: "peroid"
Junk article. Newspapers run this kind of thing every year as if all businesses were part of the retail chain. It's filler.
Show HN: Juicebox AI (YC S22), a hiring tool powered by GPT
Hey HN,

We are experimenting with GPT-3.5 and applied it to hiring, helping with: resume summaries, interview questions, offer emails, and more.

See it in action: ai.juicebox.work (works best on Chrome). It’s free to use! We are continuing to fine-tune the models and improve the quality of output.

Feedback is appreciated, and happy to answer any questions :)
Any sufficiently complex state is going to develop edge cases that your framework of choice is going to develop sharp edges.

The question is then: has some other developer provided a useful salve/balme to this?
Cable isn’t considered a common carrier service, what law requires them to carry commercials for competitors?
I think they only mentioned the horse to illustrate to people that they are using the same tool as what was used to generate those types of images. It's painting a picture for the uninitiated audience. From what I understood, this model is trained on spectrograms instead of horses and the like, resulting in this product.
Or, maybe that leads to more vasculature and more chance of hitting a vein? It's interesting that it was more prevalent in young men than other demographics.
I don't know about the company or how they make money with it (support?), but Apollo is pretty much the standard GraphQL client for frontends. It has pretty sophisticated cache and state management, type generation for typescript, etc.
It’s mostly an IntelliJ thing. All other Java apps are ugly and weird.

And there are non-native behaviors in IntelliJ too. For example you can’t close windows by double-clicking the window icon on Windows (a feature of Windows since Windows 1?).
You really think the richest man on the planet is doing weird little non-profit loopholes to wield power? You think having $6 billion in his non-profit has any impact whatsoever on his ability to influence things with his money? None of this puts him ahead financially and there is zero benefit to him doing this for "tax avoidance" if his main motive is maintaining as much money (and resulting power) as possible.

I find it god damn hilarious that Elon setting aside billions of dollars for non-profit work still manages to rile people up enough to suggest he's just being an asshole and doing it for selfish reasons
If you're affluent enough to mitigate the negative effects of no zoning, sure -- i.e., able to afford different housing if needed.

If you lack that financial security, you may be stuck next to all sorts of undesirable properties, like a busy 24-hour shopping center. I saw that sort of thing frequently in Texas.

Of course, poor people get less desirable properties even in cities with zoning. But zoning does discourage some of the more haphazard "jigsaw puzzle" construction where residential buildings frequently abut busy non-residential parcels.
> Autopilot even when it's in some final non-beta state, but it will probably be less people than would otherwise die to the same miles driven manually.

Bold claim. We would need the data to be sure. Judging by reports of Tesla owners in this thread I'd guess FSD and Autopilot are probably causing more harm than it's preventing.

> It never gets tired, distracted, or drunk.

Which would be a great benefit if FSD didn't drive like a drunk teenager.

Look for any tool humans rely on there must be predictability. And until we have enough public data no conclusions can be drawn. That's why it's in Tesla's interest to continue releasing less and less data except for the data that makes them look good.
Not only is not common but it's definitely not "extremely common." In the current wave of layoffs signaling the end of the "cheap money era" it does seem more common however. At least among the types of companies that are likely to make it onto the HN front page. I've worked for plenty of startups where we got nothing more than being paid up through the day we were laid off. And most of those withheld our last check until we returned all company property.
unfortunately I put in "sonic the hedgehog" and the result was...

... nothing? like, there's no playback at all. Is that expected?
Protocol: A beautiful starting point for your next API documentation site
lets just start a “no AI” movement. Humans appreciate effort and when everyone could become a dj, it just got boring, so some people (those exact people that you want at your show) will start looking for that when there is so much AI art that it just becomes dull.
Right. Most people get their email from work, school, their ISP, or from their OS provider: Google, Microsoft, Apple.

If you present people with a list of 30 email providers they've never heard of before, it's going to throw them for a loop.
Large software orgs get around this by having multiple projects that are either loosely coupled or completely separate. Otherwise there’s be no point in hiring more than 10 engineers at any point.

I’ve actually spent a long time working at engineering orgs that run super lean. On the upside there are never layoffs, on the downside you’re really constrained on what problems you can tackle - and that can have some major (negative) business implications.

Anyway I can’t help but feel we are slowly reverting back to the aughts where people thought you could clone Google or whatever with like 5 engineers and didn’t understand why nobody took them seriously.