skysight-inc/HackerNews huggingface dataset:
Web is being crippled too. Google is clenching its iron grip from both sides (search and browser), while Apple leaves it crippled on its own devices for obvious reasons.
It's not much cheaper if you want battery, LCD with CTP, and perhaps a LTE modem for non-wifi mobile internet. Also it would have a horrible form factor.

Pinephone is basically a smarthpone shaped SBC, with much better software situation than rpi, and you can use it as such. I ssh into mine all the time. You can connect anything you like to it via USB hub, incl. the full keyboard and mouse. You can use bluetooth keyboard, and just do normal computing you'd do on your dekstop, etc.

Except for small display and lower performance there's no differnece.
>the abortion issue is one such, and has been around for decades, and people have been vocal about their opinions, and I don't think they have got fired

Well yeah, but they can be, and their employer won't get in any legal trouble. Having controversial political statements on your tshirt doesn't mean that you will get fired or that you deserve to be fired, it means that your employer has a right to fire you for it with zero legal repercussions. And if the employer doesn't want to fire you for your political statement, they won't, it's up to them.
Eh, it has a lot of instructions, but that was only the surface of RISC. It's a deeper design philosophy than that.
Considering M1 doesn't support LPDDR5, and A15 will be in a similar time frame. I would not be surprised it will be a M2 ( Based on A15 ), or more likely a M2X.
> You can code up a web app to generate color palettes in about 20 minutes, which is a fun excercise.

I'd be really interested in seeing someone do that in 20 minutes. If you ever decide to do that, please post here.
your lack of imagination defines you.
I'm naive about the language development process. I have no area of expertise in C++. But coming from a background in Python I've seen people complain about Python getting bigger and bigger, and people have been complaining about C++ being huge for even longer.

In my naive opinion, It seems to me that both C++ and Python have reached a point where most people are satisfied with the features the language has. Most of the complaints are around warts in the language itself that people wish could be fixed (but can't due to backwards compatibility).

My question is why the need to keep adding features? Sure if something comes out that C++ is desperately lacking, add it in. But it seems like that hasn't been the case for a while.

My other question. Would it be possible for a language to work like an OS? Where there is a LTS version of the language that is supported for X years, and then a new version comes out that contains potentially (but not always if it's unnecessary) breaking changes? I guess Python was kind of an example of that with Py2 to Py3, but no one who started using python after 1.0 expected there to be a shift like that. But if from the outset there is that expectation that after 5-10 years there will be a new version that removes warts in an old version would people accept that?

It seems to me that the lifecycle of a language that is successful is
1. Be the new hotness and solve a problem in the programming space
2. Gain traction and users
3. Release version 1.0, become bound by decisions that might haunt you for the rest of the programs life
4. Accumulate features, bloat and warts
5. Have people complain about warts that you can't fix due to breaking changes
6. A new language develops that fixes your warts.
7. Repeat

It seems like the cognitive load from "upgrading" a language as opposed to learning an entirely new language from scratch (even if it fixes a lot of your gripes) would be a lot easier.

Having been playing around with Rust for a bit, I've seen the conversation come up about warts in Rust, and I think people fear if it will eventually become another C++. I think the answer is probably yes, if it endures for a similar amount of time that C++ did
I bet the author uses print debug statements some times.
Yes, we have. Her defense is that she has already shared all of her code.
The Muse (YC W12) Is Hiring Two Designers Come Join Us
Sandboxing exists.
Show HN: μGiffer
Ha! Try to pray people away from their Chrome browsers, good luck :) They would rather pay than switch.

But yes, I agree on the sustainability future. Afraid there isn't a solution other than Chrome losing market share or Google implementing the feature.
Well, it sounds like a parody product because browsers are supposed to be the lightweight, fast clients for the things we've offloaded to cloud servers.

By tradition, web browsing is the quintessential lightweight task, letting laptop vendors report "10 hours of web browsing" and the budget-conscious to say "8GB of RAM is more than enough for everyday tasks like browsing facebook"

Hearing that someone runs their web browser on a cloud server is like hearing someone has hired a personal assistant for their personal assistant.
It's exactly like Lisp:

(let* ((x (this))
(x (that))
...)
...)

In C you cannot even do:

{ int x = 42;
{ int x = x + 1; // x + 1 refers to this second x
... } }

This is because the scope of the identifier being declared already starts at the =. So even if the redeclaration were allowed without opening a new block scope, it wouldn't work.

However, there is a good reason for that: initializers can be self-referential, so they have to have their own identifier in scope:

// define circular structure in one step, no assignments:
struct node n = { .next = &n, .prev = &n };

In this regard, the scoping rule is like letrec in Scheme or labels in Common Lisp.
I also wear a Garmin watch with HR monitor. Having a couple glasses of wine with dinner doesn't seem to noticeably change my RHR while sleeping. There are probably differences between individuals.

An RHR that gets into the 85 range could indicate a cardiac problem. Might want to get that checked.
> 90% of the laptops sold Worldwide aren't Apple laptops, most of them are sub $500 laptops.

Apple’s share of the total PC shipments is closer to 15% now and their share of the laptop market is even higher.
I’m surprised that top-level comments aren’t interested in the escalation of ransomware threats. From holding data of individuals hostage under threat of erasure to corp targets to threatening human life at hospitals and now directly dangling a threat of violence against police informants.

This is easily the most vicious threat that I’ve seen.
One part of being human is the ability to rationalize situations rather then be rational about the situation. Two very different things.

Our biases prevent us from recognizing this in ourselves ever.

Not saying you're rationalizing your behavior, but I'm saying it's a possibility. The only way to know for sure is to provide data to back up what you're saying.

What is your statistical risk profile based off of the conditions your provided?
Show HN: I created Make.rs – a place where makers show what they've made
The price of ALL assets have skyrocketed this year, including collectibles like this. I collect comics and the prices in 2021 have gone bananas. I can't afford to collect anymore.

Blame the Fed for creating asset price inflation including stocks, housing, collectibles, etc. This is why income inequality has exploded, because everyone with assets like stocks have seen a huge increase in their wealth, and people without any assets which are the lower income people get left behind.
I have followed the situation somewhat closely as well and there seem to be a lot of misinformation being thrown around. As far as I can tell (correct me if I'm wrong), no actual malicious commit has been found to be deliberately introduced and merged into the tree, and most of the recent commits that triggered this whole mess were from a claimed custom static analyzers that resulted in wrong/useless patches but not necessarily malicious.

I honestly think the situation is somewhat overblown, and some maintainers think so as well. To quote Jason Gunthorpe:

> So, this revert is based on not trusting the authors to carry out their work in the manner they explained? From what I've reviewed, and general sentiment of other people's reviews I've read, I am concerned this giant revert will degrade kernel quality more than the experimenters did - especially if they followed their stated methodology.

and Doug Ledford:

> I have to agree with Jason. This seems like trying to push a thumbtack
into a bulletin board using a pyle driver. Unless the researchers are
lying (which I've not seen a clear indication of), the 190 patches you
have selected here are nothing more than collateral damage while you are
completely missing the supposed patch submission addresses from which
the malicious patches were sent!

https://lore.kernel.org/lkml/20210421180155.GA2287172@nvidia...

https://lore.kernel.org/lkml/18edc472a95f1d4efe3ef40cc9b8d26...
Significant Salesforce MFA outage
MFA is only working at about 25% capacity across pretty much all of Salesforce's product portfolios (what they call "clouds"). Investigation of possible DDOS or other attack is ongoing, no ETA on a fix.
Chip making was outsourced to Asia because it's cheaper to make them there.
You can still do things, its just that now the user has to approve it. Maybe a 'let every app have every permission by default' checkbox would make you happy but I'm not going to advocate for it. And you can still sideload an APK without even having to jailbreak the device.
> No, money will always be used for crime as long as money and crime exists.

This seems to fly in the face of the facts. Namely, that ransomware was virtually impossible to conduct before digital currency, due to the traceability of electronic money, and all current ransomware uses cryptocurrency rather than any other form of payment.
You can even go back to 2013 and not notice that you’re using a 7-8 year old machine. A MacBook Pro from late 2013 runs Big Sur and performs fine for most everyday use use case and any development work that doesn’t require an IDE. You just can’t run Chrome all the well, which should tell you more about Chrome than Macs.
You've always been able to use any of the web browsers in the store to download and install a random APK from a website (for example F-Droid), you don't even need to sideload it. Sideloading apps is mostly just a relevant concept for developers or for users who have no alternative to getting custom code on a device. (Edit: Speaking of ad fraud brought up by the GGP, there are also many automation apps, at least one (Automate) uses a plugin flow-chart architecture exposing all sorts of functionality, with users able to share custom scripts. Not to mention tons of plain "auto-clicker" apps.)
Functional programming trends killed it imo. Map filter reduce make up a big part of the code I write and it takes longer to write the hard-to-read UML version of those than it does to write the actual implementation.
Show HN: I built a tool that helps writers get feedback as they write
Read only makes sense. I imagine you would have to go into your settings to enable the API in the first place. The scariest thing for me about the current banking system is that my account + routing number acts like a key that can remove money from my checking account.

I totally agree that most banks have terrible UIs. I think the opensource community could do a much better job. I hadn't thought of notifications but I think it would be great.
Nitrox is 100% fatal at depths beyond prescribed limit. The whole point of Nitrox is to increases the oxygen content in the gas to minimize nitrogen absorption. A side effect of this is that you will get to hyperoxic poisoning thresholds earlier on a deeper dive profile. This is why Nitrox requires additional certifications, to help understand these limitations and learn how to calculate your max operating depth. (when using nitrox wihtin these thresholds I find I have more energy at the end of my dive).

To go deeper you need to blend in inert gasses and decrease o2 and n2 to keep partial pressures below fatal doses. This means most commonly mixing in Helium to cut down on over o2 and n2 in your gas mix. Human tissue I guess doesn't absorb helium the same way it does n2.

Source: Open Water Scuba Instructor with multiple agencies... I havent taught in about 5 years though so some of this information may have changed, especially in light that global helium shortages (or US stock piles?) may have driven the price of He up to high to be used for mixed gas diving.
Yeah, sure that’s what happened.
The real problem is the Redis Cluster protocol, which pushes all the smarts onto the client. This means each client implementation behaves differently and fails differently.

I would encourage Redis users to use Envoy Proxy as the Redis client (ie use vanilla client, and use Envoy as the cluster client). You get all the HA and usefulness of Redis Cluster, but way less of the headache. Also, strongly encourage people to check out Elasticache, which is really good.
I don't think they said that.

The argument is rather that the AppStore is not secure at all, but a) we still cannot sideload apps and b) legitimate apps get kicked off for no good reason, etc.

The problem is false security and false expectations.

Arguably it's easier for a user today to accidentally download a scammy app from the app store than it would ever be to do when sideloading. The latter would always come with the expectation and warning that it's not vetted by anyone, so the user and/or community will invest the time to make sure the download is legitimate.
How is it "Obviously"?
What’s so special about doing a really good job

and be excited about it enough to attend meetups, prepare keynotes, speak about it in social media, read books about it, help colleagues...

at the same time?

Why do you need some magic prioritization skill for that?
As I said elsewhere in this thread, in embedded C you can't always set a breakpoint. If there are real time things going on, you won't meet the timing as soon as you hit the breakpoint. If there are multiple threads, stopping one of the threads can change everything, making other threads take a completely different path than they would have without the breakpoint. All you can get from it is, yes, this thread hit this breakpoint, and the local variables have these values. But (at least in many embedded situations) you can't continue from there to learn anything more from the next breakpoint. You have to start over.
If you don't use YouTube, I bow to you good netizen.

But in all honesty, it is very very hard to avoid Google. Android, Gamil, YouTube and Search are big four left on my list.
A walled garden doesn't necessarily exist solely of proprietary protocols and code. In the case of fdroid, apps that violate open source licenses are not allowed.

So, technically, from the perspective of a company like Facebook, fdroid is a walled garden they cannot enter without open sourcing their code.

(I'm not saying fdroid's policies are bad. I'm just trying to make an argument for the counterside and am playing the devil's advocate here.)

PS: I know about third-party repositories. That's not the point, it's differences in policies and their effects on the ecosystem I want to discuss because I think they're more important.

Google advocates always make the argument that endusers "can just root their phones and install the APKs anyways" which is similar to f-droid with an external repository. Most non-technical endusers simply won't do that.
I hope they add support for graviton on elastic beanstalk soon.
python still has syntax and still requires you to actually write code. your trite meme aside, python is not actually executable pseudocode, and writing actual pseudocode is still faster and requires less specificity (therefore less mental overhead).

you're welcome to do whatever you want, but I'd rather do a pseudocode outline and then fill it in and have a statically typed program when I'm done, than to do a first-pass python program that is written as I go with no pseudocode.

again, the actual act of typing the code is a pretty insignificant part of development, what really takes the time is debugging all the edge cases and maintaining it for the next few years, and that's where static typing gives you a bit of an advantage. python is very much like the programmer bragging about their dvorak keyboard, it just doesn't improve on a part of the development lifecycle that is a particular bottleneck, and it does pose disadvantages down the road for maintenance and collaboration on a larger codebase. A little mandatory structure (not too much) is indeed a good thing when you have to work with other people's code (including past-you code).

And jeez, "ignore at your own risk!", maybe not intended but you just come off as dismissing a substantiative argument with a meme and a condescending dismissal.
People tend to pick on the newcomer. Take Tesla. Every single Tesla crash or fault makes the news, even though their rate of fault is less than average. It's meaningless to say "10 Teslas have caught on fire this year already!" without also mentioning the thousands of cars from other manufacturers that have done the same.

People who say bitcoin can never work because people fall for scams don't understand what the technology can do and don't understand where the technology is going. All of these problems are very solvable.
Or, y'know, a bank transfer.
The comment I replied to talks about "any other world's currency, not "every other world's currency". They must mean USD, EUR, JPY, and CHF too, not just VES and MMK.
curved wood features and structures are not uncommon, using materials like bamboo and engineered wood. it’s not easy and requires specialized skills, but it’s not a nightmare. and flexible wood structures tend to be more resilient on a per-mass basis.
I think it depends on how much changes between generations. So far it seems like most of this isn't really new, but almost exactly what's been on the iDevices for a long time. If they don't re-architect substantially between generations I can see the Asahi project keeping up.

The GPU stuff is new, but it seems like good progress is being made: https://rosenzweig.io/blog/asahi-gpu-part-3.html

For data centers, it helps that GPU and so on is just less important. It's wasted Silicon, but the CPU is competitive even before considering the added features so that's not the end of the world. There's a good chance that Apple can use that to their advantage too, by using chips with broken GPUs/NNPUs in the DC... or designing a smaller chip for data centers... or one with more cores... or so on.
Where does “10% of their global revenue” come from? I don’t see a number mentioned anywhere in the article, and the original title is “EU set to charge Apple over anti-competitive App Store policies this week”.
So they are still in detectable levels...
Elon Musk has paper hands
Exactly. Yes, cave diving is extremely dangerous. Deep diving also is dangerous. But there are dives, amazingly beautiful dives, that, while not devoid of risk, are very safe. Simple, shallow dives in the Caribbean, for example, where the benefit of the tank over snorkeling is just that you can stay down longer.

Diving is wonderful. Get certified (but you don't have to be for some dives).

I also sail. Also wonderful. Can be dangerous if you push the edge, but more likely embarrassing if you stay within your limits.
If you need to add a new field to your API, you probably have to add that field to your data model.

So you start off by adding the field but not expecting any data. You might even ignore it. In order to do a migration, you are going to need a default value for that field, so you start storing the default value. You migrate existing records to contain the default. Then you start validating and storing the supplied value, with the default if it's missing. Next you add warnings to the defaulting logic. Eventually that warning becomes an error.

Only near the end of this process can the rest of your code start making decisions based off of the new value instead of the old one (except in sanity checking exercises you perform along the way to verify that this is a choice and not a bug). Once that is done, you might start removing or ignoring the old value.

What I think is often lost in technical discussions about APIs is that the above process has built into it a framework for talking to your customers about the change, whereas often the subtext of these migrations is "how can I use technology to avoid having to talk to people".

Changing relationships without having an adult conversation with people is passive-aggressive behavior. You have a technical problem that has become a social problem. You can't fix it with technical solutions alone. Sack up and talk to people. Even, or perhaps especially, if you have a solution that requires little to no work on their part. Abstractions leak, people hate nasty surprises, and their follow-on questions most likely will bring up cases you never knew about or simply forgot. Having automation makes this conversation easier, but it doesn't obviate it.
The average transaction cost is baked into sticker prices, so at the end of the day, it's the buyer who pays the transaction costs. It's like saying 'the merchant pays rent' - yes, in a way, but really no. The customers pay the rent for the merchant via mark-ups.

However, there are a number of benefits; for one, average ticket size is about 20% higher for credit transactions vs cash (if I recall correctly) and merchants do not have to hold onto and manage piles of cash. This is a material cost savings.

Further, of that 3%, about 0.1% goes to Visa, the rest goes to the issuing bank and covers the cost of rewards programs and loan origination. Generally speaking between 1 and 2% of that will be rebated to the buyer.

For the remaining 0.9-1.9%, customers get benefits like insurance and the ability to issue chargebacks.

In Europe, debit interchange is capped at 0.2% and credit at 0.3%, and they just don't have insurance or rewards.

As it stands today if you wanted to transact in crypto, not only will you pay the $30 fee, you'll also be paying the mark-up for credit acceptance.
Yep. Unfortunately the M1 MacBook Pro currently only goes up to 8GB.
This is a very very weird product. From the site which looks like a nice pitch btw, this basically looks like a VM that only serves as a browser. What problem does it solve?

Btw. My teeth gnash at the thought that my assumption above about the product is correct.
Be me, mid 90s. Wannabe methodologist. Earnest, enthusiastic. Dismissive of OOAD/P criticisms.

Attend OOPSLA '98. Spot break out session on Software Architecture. Featuring Grady Booch! Oh boy, I gotta go.

Finally work up courage to ask my hero Booch "What is 'Software Architecture'?"

Long, thoughtful pause. "'Software Architecture' is what Software Architects create."

Poof. Bubble popped.

FWIW, the Agile Methodology™ hype cycle is self same.
That last part really blows my mind. You would think that recurring outbound transfers would be totally common right now.

I totally agree that Plaid makes sense, but it frightens me a bit that you have to give your username and password to Plaid.