skysight-inc/HackerNews huggingface dataset:
> You really need to cool it with the condescension

> But I doubt you even know the costs to run the service so my opinion is that you are speaking from a place of ignorance.

> You didn't build or work on an app store. You played with one. Much easier to modify something that already exists than to create something where there once was nothing.

That's some impressive cognitive dissonance ya got there, you might want to try looking in a mirror. You have no idea how much involvement I had. Please stop arguing from a place of complete and total ignorance.

> Look, if it's so cheap and easy to do, why is everyone so hell bent on getting onto Apple's? They should just do it themselves!

Surely you can't be serious... this is literally the topic at hand. Apple won't let anyone do it themselves. That is why they don't do it themselves. People absolutely would do it themselves if Apple wasn't behaving anti-competitively. I'm glad you agree that Apple should open up iOS to 3rd-party app stores so that they can live or die on their own merits, rather than being prevented from existing in the first place, based on dubious claims of protecting users. Though again, it is worth noting that people (yours truly included) actually have done it themselves, through jailbreaking. And that many jailbreak apps have done quite well financially, handling the distribution themselves. This is success in spite of Apple, as requiring users to jailbreak before they use your App Store is in fact a pretty high bar and does in fact make your system less secure.

> You did not say anything about sandboxing _3rd-party app stores_... App Tracking and Transparency was created for a reason.

Um, yes. That is exactly my point – the apps themselves are sandboxed and permissioned, at an OS level, so Apple's oversight (in the App Store) is a lot less useful than it once was (whether it ever was particularly valuable is not a given). If an app wants access to your location, the user has to explicitly allow it to have that permission. It doesn't matter what App Store the app is being distributed on, that sandboxing is there regardless.

Also, isn't it a bit strange that Apple added such a feature in the first place? You'd think, since they were already gatekeeping apps that can be installed on your device, there would be no need, because Apple would catch apps that asked for permissions they didn't need, hmmm... just kidding, obviously this is because different users have different needs and Apple can't prescribe the same thing for everyone. Which is exactly why Apple should open up iOS to other app stores, and in order to keep iOS users secure they should focus on more things like App Tracking and Transparency, not on monopolizing app stores.
https://www.goodreads.com/book/show/698866.The_Myth_of_the_R...
I file this one under: It Depends™

If your software development process requires that multiple people have a hand in each pull request, or these pull requests are part of a more complex merge graph, then I can clearly see the argument for NOT doing squash merge. This is plainly obvious to me and I would be on your side for not going down the squash path. Knowing who was responsible for each part is a very important thing.

If your software development process only ever has a single author per pull request, and these are only ever directed from work branch->master branch, then I would strongly argue for doing the squash merge option. This is what we do today, because we find it to be the ideal blend of hiding subjective commit styles while still preserving essential knowledge about who did what.

Occasionally, we will break our own rules (oops i didn't squash that one), but we don't make a big deal out of it. There are way more important things to worry about most of the time. There is only ever 1 specific commit hash you build your software at, so it doesn't really matter if the branch has 1 or 10,000 commits in it.
Only obvious limitation is that they only support that for HLS streams whereas YouTube normally uses DASH.
Looks like they went full Amazon, by forbidding developers to work in OSS side projects. I cannot really believe it's that no politics talk only: https://news.ycombinator.com/item?id=26944192

Edit: I was wrong. Politics destroyed them, not some crazy policies. https://news.ycombinator.com/item?id=26963708
Product Management Lessons Learned at YNAB (You Need a Budget)
The name is in short shit. If I decide to call cars electric horses they still wont require breeding, pastures, or feed and will will need mechanics, gas, and pavement under the wheels.
> You're proposing that we hire people either at random

That was your idea.

People are generally pretty well aware of their skills.

https://en.wikipedia.org/wiki/Market_abolitionism

I never talked about business, and your example of C++ programmers is very very specific.
Yes and are being actively developed by multiple teams https://eprint.iacr.org/2020/1126.pdf
I don't know. I mean search on roku is kind of it's own thing. It would be odd to expect the built in roku search to limit itself to just the app. To those who aren't familiar, there are two types of search on roku, the in app version that already does what one would expect and the device level search which searches across all available apps.

Roku is clearly doing paid placements for the device level search. It pretty obviously shows you "hey this is available here for $xx.xx" There's no confusion around when you're doing one versus the other. The device level search kicks you out of whatever app you're in and does the search from the dashboard.

As another point, I would never expect a search within YouTube to show results on YTM or YTTV. The roku just doesn't work that way.
India turns down UN supply chain help
I'd highly reccomended his video "What is right to repair? An introduction for curious people." as it clears up many misconceptions about right to repair: https://youtu.be/Npd_xDuNi9k
The point for me is that it makes my reading more active. I also get a physical feel for code style. If I was just reading source code, it would be a lot easier to skim over things without letting them cook in my brain from a bit.
Yes, definitely that.

But I think a lot of businesses really have a problem with the mechanics of just getting their business running again, like the one in the article. This seems fairly straightforward to defend against.
I don't think it matters, even with infinite pockets. Let's say 3 is the max number of losses we will accept. 50-50 coin flip, start of betting a dollar. 7 out of 8 times we win a dollar. 1 out of 8 time we lose a dollar, double lose 2 dollars, double, lose 4 dollars quit.

(7/8)(1) + (1/8)(-7) = 0

Generally: n = number of losses before quit.

E(x) = (1-.5^n)(1) + (.5^n)(-2^n+1)

= (1) - (1/2^n) - (2^n-1)/(2^n)

= (2^n)/(2^n) - 1/(2^n) - (2^n+1) / (2^n)

= (2^n -1 - 2^n + 1) / (2^n)

= 0

So with a 50-50 our expected value is 0 even with an infinite bankroll. Which makes sense, there is no way to transform a series of neutral or negative expected value bets into a positive expected bet by combining them.
If you ask me for proof I don't provide you any. Less than 3% of Roku users launch YouTube TV channel on Roku.
> Notably, text editors from 30 years ago still work fantastically. Email clients from 30 years ago still mostly work great (unless using certain popular anti-consumer cloud email providers).

What text editors and mail clients are you using regularly that (a) you paid for and (b) have not been regularly updated for 30 years and (c) still work on modern systems with modern file types and file systems?

To be direct, I highly suspect that any 30 year old applications you're referencing receive regular updates, are tragically underfunded, and the developers would ultimately benefit from upgrade or subscription pricing.

Of course, everyone loves a free lunch, but someone had to pay for the sandwiches.
It's a prime example of engineers mistaking aesthetics for utility.
100% agree. It's a trick that criminal con-men have been using forever in the physical world. There's no reason to kick a door down (draw attention to yourself) when you can convince someone inside to open it.

"My puppy just got hit by a car! Can I come in and use your phone to call for help?"
April 31st is the world backup day for most people.
Many years ago I went to a Fun Lovin' Criminals gig that was completely ruined by the idiot sound guys: way too much bass and way too much drums (bass drum in particular). Given that Huey's main vocal style is low-pitched chilled out rapping it meant that you could barely hear anything he was singing. I was really pissed off. Easily one of the worst gigs I've ever attended, and this is including pub and small club bands, but it wasn't the band's fault at all: they were absolutely tight.
Assuming this is a serious question:

Roku net income was $67m for the Dec quarter versus Google at $15.2b. Two hundred Rokus still do not a Google make. And Google did even better ($17.9b) in the most recent quarter.

Phrased differently, Google will probably earn more profit this year than Roku's entire market cap.
> and lots more…

Would be nice if they linked a changelist with all of the commits instead of this^.
> figuring out where to put the bike shed.

Anyway, the _real_ question is what color to paint the bike shed?
Make WordArt – Online word art generator
There is ample proof that Apple pays off their parts suppliers to prevent them from selling components on the open market. Louis Rossman has documented it well. Failure prone chips like USB muxers and voltage regulators that are unique to Apple devices but made by suppliers who's products are otherwise available on Digikey and Mouser somehow those aren't.

SMDs are not anticonsumer. They are harder to work with but with practice anyone can deal with them just fine. I've yet to see anyone argue for a through hole mandate.

But I have seen people argue for banning clearly anti repair design practices like gluing assemblies together. Or designing a screen in such a way that you have a high chance of breaking it when removing it.
Unrelated: that's weird, I submitted this title with "lessons learned" in lowercase but it got capitalized when I submitted it
Yeah but software engineers know that hostile actors come with the territory any time they expose a networked device or service. It's no different than corrosion or any number of other inevitabilities that engineers have to deal with.

When's the last time a civil engineer designed a bridge without accounting for corrosion or the fact that people will be driving over it?
They don't want to pay Roku money. It wouldn't be natural to demand someone clear their good name by paying money (i.e. 'support' the device) to the person who insulted them.

That's akin to blackmail.
> The regulation proposed by the NY is also strange. If you want to help low-income families to access internet, why don't you just pay their internet bills directly?

A simple model for why the Internet is so pricey in USA is that providers made a deal with government that ISP are investing into infrastructure while government passes laws favorite to leading ISPs. Those laws make competition uneven, so existing ISPs enjoy monopolistic market.

From this model, government doesn't see a point in paying for bills high prices it helped to create. Better adjust laws.
The chart doesn't show AZ data, which seems like an important piece of this puzzle.
A clock's accuracy may be tied to the entropy it creates – Science News
Do it now, don't leave the future pay for your current debt.
> A complete and utter waste of time. You spend more time messing about with rebase than solving problems.

Eh. Not really. A clean history is a good resource for figuring out what was changed and why. Cleaning up history isn't even that much work anyway.

> When you're digging through VCS history due to a bug you often ignore the commit message anyway - if the code did what it seemed to do you wouldn't be there.

Only if the commit messages are shitty, which unfortunately they often are. I try to summarize what I'm changing and what I indent those changes to accomplish, because if there's one thing I hate doing, it's spending more time than necessary to puzzle out what I (or a coworker) was thinking at the time.

VCS history can be a pretty powerful tool, but a messy history discourages the use of it.
I had no idea until I read your comment that you could click and drag the engine models! Insane!
The Web3 Index: Track network revenue across the Web3 stack
Crypto also risks the ability of central banks to print infinite amounts of money
It's a lot scarier when you see things going under load at speed. Lots of wiggling, twisty magic, waves.

Smokey Yunick (blessed be his name) used to make see-through timing covers, oil pans, valve covers + strobe light + some sort of oscilloscope setup to watch the craziness. I think I remember seeing the results for small block Chevrolet timing gears on sprint car engines as the teeth wiggled more and more with rpm. Cam went backwards and forwards. Ooof.
So mathematicians are still doubting the 4 color theorem? And the classification of finite groups?
Fixup commits are a good way to work around this. https://git-scm.com/docs/git-commit#Documentation/git-commit...

You still create your "clean up" commits, but it's done in a way where git can automatically squash everything back together in the end.

See also https://git-scm.com/docs/git-rebase#Documentation/git-rebase...
https://www.syracuse.com/news/2018/06/new_york_regulator_acc...

New York and Spectrum recently fought a battle over false advertising.
You’re right, I got my wires somewhat crossed there; I was trying to describe fungible as a lack of inherent uniqueness. That was a poor example.
Mods please update link to https://developers.facebook.com/status/dashboard/ whatever OP linked is loginwall'd
I have also never known a single layman who complained about memory leaks. People don't complain about stuff they don't understand, but that doesn't mean the problems are not affecting them.

Another problem is that small problems affecting a large number of people do not have much vocal support, while their costs are still enormous. (As compared to problems that affect a minority a lot.)
Strongly disagree. Mainline branch commit history should be clean atomic commits that you can roll back. Otherwise you are just asking for trouble on any merge conflict or hotfix scenario.
> Last updated October 5, 2006
> Why is it that even slightly old systems are so buggy that they are trivially hackable for a moderately well funded group?

because software is tremendously complex with a large surface area to attack. And many OS features were designed when wide-scale hacking was not a problem.
This might be a rare case that actually benefits from being an interactive map with lines colored differently/dotted differently to indicate interconnect speed (of course, keeping the table for non-js compatibility).
> Squash merge has the major disadvantage of getting rid of valuable meaningful git history.

There are reasons against it but the real world is messy. Developers tend to commit things, recommit, undo, redo, move things around. Is this valuable history? It can be but I would say 99% of the time it's more valuable to have a good commit message about what was intended rather than what actually happened.

The idea of squash merge is to make the history clean from the get-go as you said.
> Really you should just tax income at high rates and investment at near-0%

The article mentions income taxes are unconstitutional in Washington.
Ditto on Julia Evans and Digital Ocean.

Also, do the reddit.com/r/linuxupskillchallenge. You'll learn a new piece each day. (Rest in peace snori74)
To make it thinner.

And I 100% blame Apple for this. IMO, Apple is not a tech company, but a fashion company. Or more accurately, they produce technology that's optimized to be fashionable. Thin laptops are more sleek, but to make them thinner will require parts to be soldered to the motherboard, since an actual slot will add 3mm or whatever.

Other companies feel like they have to match Apple, and so they follow suit.

The thing is, AFAIK, nobody is asking for laptops to be only 0.63 inches (16.1 mm) thick, but that's what people are buying. Apple advertises how thin the MacBook Air is, and the masses go wild over it.
Millennials now have real jobs and real money now so there's money to be made by turning things from that time period upscale experiences for them to relive with nostalgia.

See TV/Hollywood. :/ Tons and tons of remakes. Some are decent enough (the 2017 Duck Tales was solid), but they're pretty clear cash/attention grabs...
I wonder if you could, for reasons, make a set-up where you upload your PHP files to an S3 bucket, and then have a API Gateway or Lambda which basically just serves the files from the bucket, and if they are PHP, executes them with a Lambda PHP runtime.

So you hit /index.php -> checks S3 bucket for index.php -> executes that with lambda and gets string of response -> returns it to original lambda -> serves up to client.
The Strongest Predictor for Success
I am biased because I used to work there, but the how-tos on https://www.digitalocean.com/community/tutorials are well-maintained by a team of technical editors, writers, and paid contributors.

They treat articles like code, the average article has 30+ edits, and reports of issues are triaged and turned into edits and updates.
Lets look at a specific example. Take Kubernetes: everything is yaml, with complete schemas, all the way down. From your perspective this is configuration utopia, right? Meanwhile back in reality k8s is the poster child of "yaml hell". From the day it was released, people took one look at it, gave it a giant NOPE and instantly spawned half a dozen templating languages. The most popular of these is helm, which has a terrible, no good, very bad design: full of potential injection attacks from purely textual string substitution, manually specified indentation to embed parameterized blocks, virtually no intermediate validation, no way to validate unused features, etc etc

Compare to dhall which publishes a complete set of dhall-k8s schema mappings which enables you to factor out any design you want down to as few configuration variables as you like, while validating the configuration generators themselves at design time. https://github.com/dhall-lang/dhall-kubernetes#more-modular-...
Time spent twiddling with the repo is time saved in the future debugging or writing documentation.

You can have large refactoring PRs for which splitting them further really makes little sense(*), but that have a huge risk of introducing regressions. Being able to bisect them is much easier with a properly maintained repository.

(*) And then you spend time twiddling with GitHub, which is the same as twiddling with the repo except with worse tools.
Let me help you then, take the statement I quoted:

> "We've tried the 'rawr girl power, women can do everything men can do' culture, and the result is scores of women being used and taken advantage of because they were not capable, emotionally/temperamentally, to be their own advocate in sex and dating interactions."

"We've tried" = subjective

"rawr girl power, women can do everything men can do' culture" = subjective

"the result" = subjective

"because they were not capable, emotionally/temperamentally" = subjective

"in sex and dating interactions" = subjective
Will increase the utility of decentralized exchanges like Uniswap and DeFi in general. The more CEX gets regulated the less people will want / need to use them.
Yes, but if you have a VISA card you can still withdraw the money and pay in cash right? That's an alternative that doesn't involve switching over to another ecosystem.

Also, the EU regulations cap the fees and set up identical rules for everyone (unlike Apple where its own services are left through without a second thought even though they don't necessarily operate to the code).
I'm hitting a login wall; is there a way to access the content for people who don't have a Facebook account?

Alternatively, is there another page that tracks the status of the issue? I found Platform Status [1]; or perhaps "JS SDK and Social Plugins Failure" [2] is more accurate.

For the record, at the moment the submission points to a discussion on Facebook Developers forum [3].

[1]: https://developers.facebook.com/status/dashboard/

[2]: https://developers.facebook.com/status/issues/49265292218744...

[3]: https://developers.facebook.com/support/bugs/484663959337678...
"Changes at Basecamp" : https://news.ycombinator.com/item?id=26944192 ( 4 days ago, 774 comments ).

Which is a feel good piece about management philosophy ( a bit back to our roots ) and does not mention layoffs once.
> hosted instances of web software

Do you still have anything online? I looked at http://fundamental-code.com and didn't see anything, but maybe I missed something.

I'd be interested to see if there are ways to simplify the open source -> saas process.

I built a quick & dirty landing page, I'm curious if something like this resonates. Any feedback?
https://saasform.dev/transform-open-source-in-saas
The way I've seen the rules inforced (though inconsistently) it would be more like walmart not letting Coke put their website on the can, because you can buy coke directly from the website.
We don't need a tinkerers option we just need unobstructed access to the docs and access to purchase proprietary parts to replace failures and those parts should be available at a fair price.

I vote yes for right to repair, both with my dollar and my desire to favor the rights of the citizens of this country.
I am not familiar with the SF tax code, but doesn't Prop 13 essentially only limit property taxes for people actually living on their ground? Can you give any reason why someone should pay higher property taxes every year just because the surrounding prices skyrocket? Aren't you essentially demanding to disown people?
You're basically arguing for IP protection via obscurity/complexity, but I assure you that anyone who wants to clone tech products at industrial scale can already do so today. This just gives repair documentation and parts availability to independent repair shops and DIYers...
Because China is offering 3x the pay. Obviously this isn't sustainable. But China can pay higher (through government help) that disrupts things. The pay is so high no company could sustain business. It already creates a situation where competition is out the window.

The US and China should invest in their own fabs and become less dependent upon TSMC (which is happening and even if both dumped enormous funds into this it would take quite a long time to overtake TSMC. Which is why China is doing this in the first place).
Spot-on for both counts. Preserving a PR's individual commits in the master branch is insane - many of those commits won't represent a fully working system anyway, so why keep them in master?
Kind of like resumes that list "GitHub" as a skill.
Crypto is like an unregulated bank with no depositors' insurance. Those were forbidden (in most places) for a reason! What if a crypto software network goes all ... Geocities ... on owners? Or pick any other discontinued web or software service out of the wreckage of tech disruption. There isn't a M&A strategy to rescue these things....
If that happens and there are no laws, it will affect more and more products.

Don’t buy a laptop? A car? A building? A slab of wood?

Yes, my examples are borderline unreasonable, but we’re already at the level of unreasonable products being licensed instead of owned (Tractors, DSLRs).
If you got a $300k liquidity event. You will pay $3,500 in tax on it.

If you worked at that job for 10 years at $30k less than normal, that is $7,600 a year that you didn't pay in federal income taxes on that missed income.

Do the math, had you taken the income that would have been $76,000 in taxes over ten years vs $3,500 in taxes in one year.