skysight-inc/HackerNews huggingface dataset:
> I also don't understand all the complaining about ads and trackers.

Then be clear about your intent to make money. If you have a product, sell it. I'm tired of being treated like a rat where my life is a maze with god knows who or what watching my every move trying to think of ways to coax money out of my wallet while selling that data to fatten theirs continually. Stop with the "strings attached" freemium crap, analytics behind the scenes tracking, and dark pattern BS. I used to be happy to pay a few bucks for a good app. Now everyone thinks their entitled to continual money streams from ads.
that was my point. "open source" is a loaded term.
Any decent lawyer would look for an opportunity to turn this around on them.

He *may* have broken the law, but if he didn't commit financial crimes with the information he obtained and was falsely accused of them, lost his job over it, and was prosecuted for the false claims then he definitely has damages, some of which would fall under libel. This could go not so great for "Whistlr" if the information found in process shows that they maligned him.
Deno is betting on edge computing to explode and offers a good offering (Deno Deploy) in that space leveraging how it has a smaller API and faster startup times than Node.

It also thinks that edge computing is a good space to leverage the myriad of web APIs it supports + there are certain workloads that it does better than Node (like single executable)
Not OP, but in the end it comes down to :

1.: No - but you need people understanding your business and GA as well as being able to implement additional tracking events via Google Tagmager (for example) to be able to answer questions like: What percentage of our users came via paid social media advertising, viewed a product, added it to the shopping cart, but abandoned the checkout. And how many of them are newsletter recipients so that we might be able to send them a reminder, that they have items in their shopping cart.

2.: No official nomenclature - just deeper data analyst's knowledge to ask the business people the right questions, develop an understanding of what to measure, talk to the developers to have them help provide (if necessary) additional info in a dataLayer structure and implement the necessary tracking events in the tagmanager.

After that said analyst needs to build the necessary dashboards/reports so that management/business can have the initial questions answered.

Data/Web Analytics in a nutshell (and described way reduced).
Sure, but your anecdote does not refute in any way that they can fail. It’s all about risk vs. overhead of avoiding that risk. The overhead of pushing often is very low, so even with the low probability of a drive failure, there’s not much reason to not do so (or any other form of backup, really).
The entire low-code/no-code markets are Excel competitors.
Yep, I would just cancel. Problem solved. I don't watch enough TV to even consider not being able to share a streaming service with my immediate family, and I think they would all agree. There's nothing wrong with the current model of limiting active screens. This is a greedy move for Netflix and if it's implemented it would completely change my opinion of the value of their service. I would sooner just watch youtube videos for the 30-60 minutes a night that I spend with the TV on.
The one about CS students is very poignant https://www.netmeister.org/blog/cs-falsehoods.html
Given that Vim's biggest barrier to entry is its learning curve, I don't think starting out by teaching people 8 ways to do 2 things is the right approach.

Agreed that exiting should be the first thing taught to new Vim users though.
If we haven't devalued our USD currency against the EUR because we printed while they also printed, is there a currency that we did devalue ourselves against (or a country that didn't devalue their own currency through printing?)

Does printing always actually equate to devaluation?
and you'll have to solve CAPTCHA, obligatory.
I've literally never seen or at least noticed these so I'm guessing you can disable them easily which I've likely done when I first installed it.
The innovation here, which I completely agree with is:

“fund them so that they can dedicate resources to the project, and trust them to direct those resources like you'd trust a senior engineer to execute on a broadly scoped project.”

The basic concept is you pay based on trust in the skill and body of work, not pay for something.

Generally, I find companies are incapable of making this decisions except with 5+ year veterans.

Even then, I question whether or not they are truly paying on that basis or it’s just implicit.

If I’m wrong, and I would very much like to be, who are examples that take the path recommended here with their devs?
Pretty similar to you, I commit as often as possible, but I also push whenever I commit so that its backed up. Then once its ready for review, I do an interactive rebase to try and group the commits into useful chunks for the people reviewing, and to improve the commit messages.

Git is crazy complicated under the hood which is awesome when you mess up and need to recover something, but in general my goal is to use as few git commands as possible and keep everything as clean as possible.
tl;dr use ableism to disregard your critics
How could the FTC require algorithmic destruction? How do you prove you destroyed something? Would you have to lobotomize everyone who had worked on building it?
I don't see why that is relevant. The point was that if companies have a monopoly in a product category, improving the product doesn't make the company more successful. Since macOS and iOS do not have a worldwide monopoly, Apple (and thus Tim Cook) have to improve the product for the customer to gain more marketshare.

I think Apple's problem was that one designer that was a fan of excessive minimalism wasn't matched enough by a counterforce. Now that Ive is gone, Apple takes a more functional approach to product design. E.g. the MacBook Pro has useful ports again.
So they popularized (or maybe co-opted?) the term then. They didn't coin it. How is this nitpicking? Saying they coined the term is clearly false.
The problem is that every Excel user is an Excel native. Your product would have to be magnitudes better than Excel to compensate for the cost of forcing everyone to give up their fluency in the software.
Imagine if people used Reddit to store their photo libraries…

This move seems like common sense to me. The question you’re asking is really whether you can view this kind of content without a paid account.
There's Dart: https://fuchsia.dev/fuchsia-src/development/languages/dart

The UI uses Flutter.
I would love to see a page on your website where you compare yourselves (in a fair and transparent way) to the best plant that does the same thing. I am not knowledgeable in the field. But there will be some algae or mangroves that get CO2 out of the air.

I would love to see that comparison. Incl. the aspect that the plant does not need to be repaired, multiplies on its own, etc.
> While these are experience values and not strict rules: Astonishingly older users are performing better with TUIs than GUIs, and the worst are usually websites and web-applications. By "better" I mean fast in usage and less prone to mistakes.

The #1 thing that messes my (elderly) parents up, using a UI, is inconsistency. In modern software, this comes in two main forms: frequent updates that modify the UI, and screen-takeover notices (often about updates that have modified the UI, or to beg the user to perform an update that will modify the UI).

These are much rarer in TUIs.
Easy way to get some serious premiums from MSFT buying your company if you ever tried to build a viable competitor. That said though you would watch your product get deep sixed if you sold
Look, I think assigning a mentor isn't a bad thing to start. It gets people who are interested or required to "mentor" (defined here as supporting the development of less tenured/senior employees) connected more easily with the target folks who need/want/are required to have mentors.

Then, if it sticks, it sticks. If it doesn't stick, it at least provides some context for both the mentor and mentee if that relationship or the idea of mentorship wasn't executed well.

Agreed that many times, it is an onboarding helper and someone who just acts as a friend you can ping in the early months of starting.
I think they will slowly close the functionality gap until Deno does the most common 80% of stuff Node does.

Then you factor in how Deno will be fundamentally more performant - we will see large companies who can't squeeze another cycle out of Node write blog posts about how they switched to Deno.

And lastly, NPM is a tire fire. The left-pad and faker hits will keep coming, on top of an almost daily procession of new security vulnerabilities in deep dependency trees. Something so bad could happen here that ppl sour on Node.

So I think Deno stands a chance. They just need to keep implementing and bide their time. A moment could come.
This is wonderful. The window management on macOS has been driving me nuts at work after decades of using Windows.
If you are afraid to lose what you've done, you can stash your minor changes to keep track of the small things that you already got working, and then, when you got enough working to make a commit, you do it with the best code you got. And for the many pushes, you could backup your projects files everyday. I think is a much more appropriate way to use the tools that git gives us.

That way, you won't be afraid to lose your recent work by messing something up, because you have the stash, and won't be afraid to lose your whole project/progress because you have a recente backup of it.

For instance, I have a backup script that runs everytime I shutdown my work computer so I won't have to worry if suddenly my hard drive gives up on everything.
I used to do traceroute to addresses far away like Japan or Australia to which way it takes. Packets often went through the US even when you'd think there's a shorter route.

These days traceroute to a random .jp or .au just gets you to the nearest CloudFlare or AWS, which is a bit sad in a way.
My "atomic" level is that it can build. I try to minimise time between commits/pushes because often I work on two different computers. So I don't try to keep it clean, and often cleaning is its own commit.

Android is a little weird in that a build may take 6 min on the production app though. So a lot of code is written and tested on an external repo where it might take 20 sec instead and then copied in when complete. Looking clean/complete isn't the intent but that's how it ends up.
To be fair, I had a royal pain transferring file over Bluetooth from Android phone to Ubuntu laptop a month ago. And MTP was almost as painful too.
I have no opinion on this matter, but I assume the parent implies that those agencies should not have approved this deal.
Which is very nice, tho not new. Thought I use it less often than I did when I first learned about it. I just have emacs under tmux scattered around the boxes I am working with.
When forming commits, this is the rule of thumb I have: can the entire diff of a commit be understood and explained, both in content and intent, by its commit message, ideally by someone months or years from now? If not, the commit is not properly “atomic” or the message deficient in some way.
Then I come back to it 10 years later, because I'm writing the second edition of the book, or I want to change something about my reporting infrastructure.

Those seem like one-off PDF conversion use cases that MS Word or Acrobat can easily handle. Not a high-volume, daily PDF invoice use case.
Put is the best. Their secret sauce is they cache all popular torrents so they appear in your locker instantly.

It is especially good combined with Chill Institute. I can get nearly anything on my television from idea to streaming in < 15 seconds. I can’t program, but I’d like to figure out how to turn this into a Siri shortcut…
I noticed this recently on the React docs site on mobile [0]. It's also used on Github mobile's view of repository for switching between Code, Issues, Pull Requests, etc [1].

[0] https://reactjs.org/docs/getting-started.html

[1] https://github.com/multiprocessio/datastation
If anyone wants to work on this (make web streams faster in Node) it'd be welcome. The main reason web streams are slower in Node is a lot less work has been put into making them fast. They're mostly seen as an interop layer.
in the sense that some corporation is turning into the real world equivalent of the fictional Buy N Large from the movie Wall-E
GitHub actions has been like this for years now. Years. Years!!!!

And the crazy thing is you see people on HN demanding that some one person side project/SaaS has to be at 100% uptime with multiple failovers, automatic scaling, etc. etc. There is such an emphasis on scalability on HN and yet... you just brush that all away because "software is tough." Yeah, no shit. Poor Github. They are also Microsoft now. One of the wealthiest corporations in the entire world. And people are paying Github. This isn't Twitter fail whale we're talking about.
By neutering consumer choice, neutering consumer protections, killing smaller business, making it hard for new companies to compete/innovate, etc.
You literally stated that the relevant law isn't changing...right before bringing up how the relevant law is changing, so I'm not really sure there's much point in continuing this discussion if you're just going to ignore countervailing facts to maintain your contrarian position.
You have to assert that you have copyright on the work. Which seems to be missing from that quote.
The data migration might stem from the fact that the underlying data model is so totally different, that it just might not be possible to migrate anything.

GA3 and GA4 are so different, it isn't like the US and Russia, it is Earth and Jupiter (not in terms of impact or size, but just vastly different).
Probably helps that Tim Cook was mentored by Jobs himself for more than a decade and personally saw the rot set in at IBM first hand.
Do you have any policy regarding collaboration with the fossil fuel industry?

(I'm asking because most past carbon capture projects are actually enhanced oil recovery projects, and the accounting they do for co2 avoided is... sometimes really creative. From what I'm aware Climeworks is not directly collaborating with the fossil fuel industry and does not do EOR, which I think is why they have a relatively good reputation.)
An expression like my_func(a++, a) is confusing on all fronts - the intention isn't clear for the compiler, for the code reviewer, for the programmer themselves when they read it 5 years from now, for the next-in-line bloke who gets handed this code to maintain it, etc.

My point was about whether C++ screws you over with UB when the programmers intention can be argued to be obvious. I don't think it does. But I will stand corrected if someone can show me what they're talking about.

It seems like people are making this into a discussion about C++ being a difficult language to learn - which I am not defending.
I don't understand your point here. Are you simply saying that companies can prevent this by...hiring an expensive lawyer? That seems like sort of a strawman argument; hiring a "white shoe law firm" doesn't make an FTC action go away. Companies could hire one of those anyway, but now if the firms fail to win their case (which does in fact happen) the FTC has much sharper teeth which with to move forward. The risk profile for companies engaging in data malpractice goes significantly up.

Outside of that, the headline seems very accurate--algorithmic disgorgement is a very new approach (the Everalbum ruling was in early 2021), and with the Kurbo ruling, one it appears is going to be much more common moving forward. The whole area of regulating algorithmic use is pretty novel--the whole field is basically so new that agencies are still figuring out the way to go about.
Since it's in an early stage, would be neat if there's list of features that this project wants build and which ones of them are already done. It would help to manage users' expectation when they try this out and perhaps even invite people who have been-there-done-that to help you achieve the remaining goals.
I agree-ish - I think you could reasonably hold that the material world must exist for some reason, though I think such a view is weaker than holding that a perfect being like God must exist.

More impossible from a materialist perspective to me is the experience of the self - I experience myself in a non-physical way. I can tell (though I cannot possibly prove to anyone else) that I have a self-aware internal life. From the outside it would be indistinguishable from a simulation of one (via computer or via atoms/molecules/neurons), but for every person's internal life they have a self-experience that I don't believe can be explained without the supernatural (a soul or similar). Certainly it's extremely connected to the physical, and chemicals/impulses etc shape my entire experience, but the experience itself is not physical (IMHO).
I see no value in shorter "clean" commit histories in a feature branch. In fact, if you need that, it might imply that the PR is too large to look at holistically, which is a red-flag.

Half my PR's probably have a commit that just says "mashed potatoes", or 5 commits in a row that say "maybe it works now?". It doesn't matter, its going to get rebased/squashed to a single commit in the merge process anyway (which IMO everyone should be doing, true merges from feature branches to mainline are bad).
Not if copyright is not claimed.
This made me realize I haven't heard about git-flow[0] in ages. There was an era when it seemed like everyone wanted to use that for everything, even when it didn't make any sense.

[0] https://nvie.com/posts/a-successful-git-branching-model/
But most crashes can be turned into an exploit.
Because as far as they know they did. It came up in meetings they had saying "what should we call this?" per your own link!

https://en.wikipedia.org/wiki/Multiple_discovery
It depends on where and when you are that you can do this?

You should get support before and during, including monetary support if you decide to follow through. It will involve checks on you I'd expect to take at a month or more.

> someone dealing with trauma from whatever they are running away from.

Trained social workers should be guiding you and them. You won't be asked to house an African child soldier first up. The time won't be "indefinite"

Just do it... studies show you will gain from it. A life experience.

But if you choose not to there are plenty of volunteer programs helping refugees with the language and integrating into the community.

I would be careful of fly by night Ukraine refugee organisations that might be around at the moment. If you were to go down this path you will need to be more resilient. There are stories of people picking up and housing refugees from train stations, I'm sure most stories are made up by the media, but some seem real. This should not be happening.
Where'd you get the 900k figure?
depends on function for me:

- new features tend to be one clean PR since there's so much experimentation on what will work and lots of commits tends to slow things down -- a nominal disk backup is helpful, or even just a commit when taking a break on a branch of your own, no PRs until clean

- refactoring tends to be lots of test / experimental / ugly branches with incremental PRs, since tends to be easier to say, ok, change this one thing

- been experimenting with some third in-between mode, say add X with a bit more of a planning / sprint mindset vs. oh wow, let's see if this works

- feels like this approach is more of works for startups, probably harder to do in enterprise / large teams?
Matter smart home standard delayed until fall 2022
Question: what is "ideological" about the facts stated in the README? Putin invaded Ukraine. Lives are at stake. Being against that is no more ideological than the need for you and me to eat and sleep.
My flow is:

1.a. a lot of dirty commits/wip commits

1.b. a few of clean commits, when I spot changes that I know they are already a commit by itself

Before opening the PR:

2. `git log -p`: I inspect the commits I've done and I decide what should go together, what should be edited and what can stay as it is

3. `git rebase -i`: I apply the changes I've decided during 2

4. repeat 2 and 3 until I'm happy with the results

5. the last `git rebase -i`: reword almost every commit, as almost all the commits at this point have placeholder descriptions

I'm very happy with this strategy. It requires some time to get used to it but at the end my PRs are very clean and well-thought.
Another big downside is that restarting is annoying, you can't easily switch between different things you want to do (like say run a script while you wait for something in a game), and maintaining 2 systems is more hassle. That's why I just use WSL on my PC nowadays (though I have just Linux on my laptop).
It should be statically typechecked of course, but especially in the quantum physics code we couldn't encode all the invariants correctly and runtime exceptions can still occur in rare occasions. A fix has been proposed and will hopefully be merged in time for the next universe release window.
It can be OK in some cases, but it can be hard to discover unless it's very obvious. Thanks to Apple hiding scroll bars, if the elements in a horizontal scroll happen to line up with the edge of the screen it can be impossible to tell that horizontal scrolling is even an option unless you trigger it accidentally.

Edit: Oh yeah, and horizontal scrolling interacts unpredicatably with horizontal gestures on mobile. E.g. forward/back in iOS Safari.
Lossless JPEG transcoding is the killer feature moving forward from existing images. I can't wait for jxl's broad adoption.
Given the dilution problem, I’ve been wondering if a decentralized approach is ultimately better. Can we build some cheap system that people could just simply put on top of their homes and let the wind do the movement? Individually each system would remove little, but if enough participants were involved (perhaps it’s even government mandated to have), then the costs would be shared as would be the scale.

Would love thoughts.
“Time formatting error” caused rail delays in Poland
I find it interesting that Amazon is pursuing vertical integration while elsewhere in the media industry we see companies like AT&T doing the exact opposite.

It'll be interesting to see if, ten years from now, Amazon is any more successful. So far, it's not been clear that this kind of integration is, in fact, a net benefit for the acquirers, and it certainly doesn't benefit consumers.
I yearn for the days when a policy change was written as a policy change, without looping in as many political dogwhistles as possible
Beware the survivability bias:
Maybe big companies can be destroyed by sales and marketing is just the observation resulting from small companies never getting to become big ones due to lack of good sales and marketing.
>Bond was the only thing keeping that studio alive

Tom and Jerry was also pretty awesome. Does nobody watch that anymore?