skysight-inc/HackerNews huggingface dataset:
So in the case of the parent's comment, your solution is to ban buses?
What about, instead, respecting road rules when you use a bike?
so is it still around?
Being these two the most important functions [1], [2].

The rest is merely overhead :)

[1] https://fuchsia.googlesource.com/fuchsia/+/refs/heads/main/z...

[2] https://fuchsia.googlesource.com/fuchsia/+/refs/heads/main/z...
There are several parts to your question, let me try and answer each of them as I understand them.

Fuchsia is built with a minimal core (sometimes called a microkernel) and many user-space services interacting with each other over an IPC protocol (called FIDL). The open-source part of Fuchsia, available on fuchsia.dev, is a standalone system which you can build and run on supported architectures. It contains all the services required to start a user interface, interact with the network, etc. Currently, the main supported hardware architecture for people wanting to build their own version of Fuchsia is the Intel NUC: https://fuchsia.dev/fuchsia-src/development/hardware/intel_n....

For a retail devices, such as the Nest Hub, vendors can build a custom system with additional or different services from what is found in the open-source release. Thanks to stability of the FIDL interfaces, those closed-source services do not prevent the core system from being updated. For more information on services and packages, you can read https://fuchsia.dev/fuchsia-src/concepts/software_model and the pages linked from it.

Some of those services are drivers; others may be in charge of communicating with Google Services or customizing the UI; and not all of them are necessarily open-source. So if you wanted to build your own version of Fuchsia for a Nest Hub, you'd need to replace the closed-source components. As far as the Nest Hub is concerned, I'm not sure what the exact status is. I believe a significant part of the drivers have been developed in the open (which is how 9to5google was able to guess in the past that we would be targeting this platform), but take this with a grain of salt, I didn't work on drivers. The part that interacts with Google Services is closed source. I'm not sure this is much different from the situation with Android: not all drivers or UI used on Android devices are open source, are they?

Finally, as you note, the bootloader can be locked on retail devices, preventing you from reflashing the system with your own build unless it is signed by an authorized key (mostly for security reasons, as far as I understand it). This is a product decision that is not related to Fuchsia itself, it depends on each manufacturer. I don't think it has ever been supported to reflash a Nest Hub, and the migration to Fuchsia shouldn't change that.
> Does that operation even have a name.

numpy calls it 'broadcasting', although this particular operation doesn't work. For example, this is valid in numpy:

`np.array([1,2]) > np.array([[1],[2]])`

The idea is that an attempt is made to handle the operation even if the arrays / matrices are incompatible. Extending the operations of matrices and vectors in this way allows for extremely concise operations that would otherwise be a pain, like in the original R example.
Likewise with VSCode, Edamagit is very close but isn't "muscle memory" close. I run into things that aren't quite the same as the original: choosing a remote on a new repository when pushing or selecting switches using the VSCode native pop-up.

I really want Edamagit to work. I'm still getting my feet wet with VSCode but Git integration is a bit of a pain.
Nah, it's an hardware-related project, so it will get entrenched even if it's fundamentally different from other hardware-related Google projects.

Eventually you'll be able to buy Google devices that run Android, Google devices that run ChromeOS, and Google devices that run Fuchsia. It will be confusing, but that's fine, because it will all work great as long as you stick to Google's cloud-based services, which is what really matters.

Directly or indirectly, OS fragmentation actually helps Google's business model.
That's a good point, and I'd imagine instruments like a church organ would suffer from this too, though I know in that case there are a bunch of other sources of delay, like the time it takes for the pipes to fill with air.
I’m not the author, but yes it might.

The regime is getting crazier and they eventually might start cleansing folks who said something online. Or their relatives.
You just never know.
"We then begin a process designed to safely and completely delete the data from our storage systems."

https://support.google.com/accounts/answer/465

Disclosure: I work for Google
We put Etekcity remote controlled sockets in a few places and stopped there. That being said, apparently you can buy a radio module to control them from a raspi, but we haven't gone there yet.
The Good Place (the show) took a try at this! It’s an exceptional show in many ways, and the final season spends a lot of time trying to solve this exact problem and grappling with its consequences.

(I won’t spoil it for you, but Wikipedia has a summary if you don’t want to watch.)
I'll re-phrase: why should I care about the requests of my users?
Now you know why they prefer your competitor over your better UI.
Your UI may be better, but your UX sucks.
It is based on C++ attributes, which is somehow based on C# as well.
IoT World Today: Why Do We Need to Build IoT Projects?
This article is about the prospects of IoT and why we need to build IoT projects. You may think the reason is new technologies like 5G but that is not the case.
The package installer now asks you if you want to move the installer to the trash after installation (it's been this way for a few OS releases now). This will eject the .dmg and delete it for you as well. I think it only does this if the .dmg is in the Downloads directory though.
What is the point of firefox if it comes with spyware?

This supposed feature is nothing more than a css tweak that somehow needs to upload your urls to this 3rd party provider that is not bound by the privacy guidelines of Mozilla.

It is makes Mozilla a bunch of liars in a way that Google isn't lying. Actually. Google isn't sharing your data with another party.

I wont be switching back to Firefox until they remove the pocket thing and enact policies preventing this from happening again.

Now it's just a worst chrome, with better promises that turn out to be bigger lies.
I actually don't think I went too far. I think that, perhaps through unfamiliarity, you have massively over-estimated how technical the term "bar end" is in the context. That's honestly the only way that I can reconcile your characterization of the examples I gave as "extreme" while continuing to maintain that suggesting the same be done in this article is perfectly reasonable. Within the respective contexts of those articles, "bar end" is a much more well-known term than "pythonic." "Font proof," I suppose you could argue it depends on whether you define the target audience for the article as programmers or specifically people who deal with fonts. But either way we can at least say that it's specific to a very fine context, that, at the very least, is only a subset of the topics covered by the blog where it was written. Unlike this biking article.

Also, yes, it does come across as entitled. For example:

> And I don't assume these people feel entitled. I think they just want writers to...

Right there, the direct object of the sentence, "writers." That's the problem. This isn't just wanting to know something, or deciding that an article doesn't suit you and deciding to move on. Both of those would be fine reactions. This is expecting another person, someone you don't even know, to do extra work and tailor their creative output to your tastes, for no other reason than that you feel entitled to ask them to do so.
Arm freezes hiring until Nvidia takeover
>a cruel spectacle of what happens when you throw average people into the ring of elite competiton [sic]

Good comment. I'm curious what your take on the use of social media as a means to share outrageous lies and engage in trolling behavior. Is this also an expression of a kind of status? Genuinely asking. I never thought of it that way.
Maybe this is a requirement for health-related fields, but I’m not aware of something similar in my field (Computer Science or Discrete Math).
Kind of strange that the Dutch are blamed for this, when the British took over mid-1600 and the Americans after the independence war end-1700.

Those are two moments where this whole notion of feudal estates could easily have been abolished, but for some reason the new rulers decided against this.
Opened midway through the PowerPC era. Lingered for the entirety of the Intel era. Finally fixed at the dawn of the ARM era.
No. Anyone is free to start a journal, open source of you prefer.

What they have is the only prestigious journal in a field.

That’s like saying Apple has a monopoly on laptops.
A company that builds houses would very much avoid building those pointless and expensive security features. Why would they spend a second of their architects' time on that?
Short answer: Just do it.

Now that you've read a book, pick an extremely simple task and just do it. For example, maybe try writing a command-line program that will just play a square wave through the speakers. Then, build up your skills by making options for sawtooth, triangle, and sine waves. Finally, in the callback from the audio API, poll the keyboard to decide what tones to play. ;)

FWIW: A few years ago I wrote a functional keyboard and mouse synth program that just did sine, triangle, square waves and harmonics. It sounded a lot like an organ. (I later lost interest.) What helped was that I found a wrapper for MacOS CoreAudio that dramatically simplified the API so all I needed to do was provide a stream of floats. (I don't remember the name.)

Don't fall under the illusion that you can just read books and at the end you'll know how to do this. You'll need to work through simplified tasks to build your skills and understanding before you can write your mini-synth.
I've actually had a really positive experience using a smart thermostat. The main benefit is having a temperature schedule, which my previous dumb thermostat didn't have. It's also handy being able to adjust the temperature from my phone whenever I'd like to. I find controlling it by voice kind of pointless. On the phone, you can easily see what it's currently at, then adjust it for the next e.g. hour, after which it'll switch back to the default schedule.
Basically what we need is TypeC. :)
In general I think data science code is more "research-oriented", meaning that it is not run continuously like a software app and its requirements often evolve as more information is learned from the data. Research code produces results maybe once or twice a day (manually triggered) while software apps potentially service hundreds of thousands of requests a day.

Research code, because its requirements are not fixed and it is not frequently run, doesn't need to be as "stable" as a bonafide app. For a bonafide app, requirements do not change as often and the app is run virtually 24/7.

Once the research code becomes "productionized" however - i.e. it is deployed in an online system where uptime & accuracy matter - then I think absolutely it becomes more engineering-heavy and looks quite a bit less like this code.

Would be curious to hear others' thoughts on this distinction between research vs. production code however.
In Italy we have something like that, that should translate to usucaption[0] or acquisitive prescription. The term for real estate is 20 years, for other types of property it is shorter.

[0] https://en.wikipedia.org/wiki/Usucaption
No matter the quality of the code presented here, thanks to The Economist for posting this! We all really appreciate it, even if we don't always seem like it :)

Even if it seems justified to shit on the code as is (bad style, lack of comments, no tests, whatever), all it does is discourage similar companies / researchers / folks in academia from posting their code as well. So then we end up with the same code, but now no one can see it - which is the worst of all worlds.

Let's support / work towards a culture of sharing our code before anything else. And if there's something you think can be improved, maybe consider opening a PR with improvements to really _show the value_ to all these parties of posting their code!
> For a further two years, the superior had the option of claiming compensation; this was fixed at a single payment of a size that, when invested at an annual rate of 2.5%, it would yield interest equal to the former feu duty. Because inflation had eroded the value of duties, which had been fixed many years before, this payment was in most cases extremely small compared with the current value of the land.

This is interesting in that it isn't really "abolishing" payments in so much as you are required to establish an endowment so to speak. Really it is inflation (enabled by fiat) that allowed one to escape this duty it seems...
funnily enough, this hasn't come up on italian newspapers.

I checked the Corriere (corriere.it), Repubblica (repubblica.it) and il fatto quotidiano (ilfattoquotidiano.it) since they're three different voices with vastly different opinions on what to report and what not to report.

interesting.
It's probably time to stop recommending Clean Code (2020)
It's great that it made Spotify activate a useful API they had little good reason to terminate. However, that "victory" always left me thinking a lot of people missed the point, including the person who challenged Spotify, as well as Spotify employee who responded to those emails, who confirmed they had little good reason to disable/remove the API.

To summarize, Spotify can of course terminate any API they so wish, and there is absolutely nothing in GDPR that compels them to keep it up. As long as they of course still follow the requirements by GDPR. As annoying as a workaround would be for Confiks, emailing the data within those 30 days to SongShift is acceptable and in compliance. There is nothing in GDPR that says "data transfer options once enabled cannot be removed and/or changed".

Quoting the clause "the data subject shall have the right to have the personal data transmitted directly from one controller to another, where technically feasible.", always seemed off with what is being demanded, because, they would be complying with that requirement by compiling and archive of the data, a big dump, and send it to SongShift. "I demand that you re-enable the API", on the other hand has no basis whatsoever in GDPR. The quote follows with "... or allow for some other method to allow me to exercise my rights under the GDPR", which is exactly right.

Spotify re-enabled the API because they chose to, not because they had to.

To clarify: I think it was great that Confiks convinced Spotify to re-enable the API. But, the arguments presented were not particularly convincing, and I took this as a case of Spotify doing the right thing, rather than a "David vs Goliath".
I find the same personally, but then I've seen people who would never consider themselves programmers fluently create things in Max, so I guess it depends on your background.

Max actually does have a Javascript API, it's a bit old fashioned and you couldn't use it for any DSP related stuff, but can be useful for some stuff. I used it to build a prototype of something that I'd have no idea how to build visually in Max (basically a macro parameter fader for Max for Live), but is fairly straightforward in code, and took some time to figure out a nice(ish) workflow for working with it with Typescript: https://github.com/tomduncalf/livefader

I wonder if you could use that plus the "gen~" object and/or dynamically generating Max objects from JS to do more advanced synthesis-type stuff. May be more trouble than it's worth though.
I think HNers will enjoy these detailed reviews of Steelcase and other ergonomic chairs:
https://blog.szynalski.com/2019/04/review-steelcase-leap/

Gives you a bunch of things to look for when evaluating chairs.
I don't disagree with you, but on the same line of thinking, why not call it "A system that solves all hacking everywhere, permanently"? When going down the rabbit hole of disingenuousness for the sake of wider reach, the more you lie about the actual subject, the less you are actually talking about the subject, and the more you're talking about something that doesn't exist.

It is very bad marketing to describe a precise system using very little precision.
Also most of them are not particularly fun.
This is the bigger risk. I don't see Fuchsia as a walled garden OS as it's pretty well designed to avoid that. Userspace everything with a microkernel makes for a nice small security footprint for IoT devices that can be perpetually updated.

The issue is how long google keeps up "perpetual".
Did they decide against it, or did they just not pay any attention to the area at all?
>It's also bad, because besides it essentially being theft, the grey market opens the door to bad actors who pass off used/defective/rejected/counterfeit parts as the real thing.

If they actually stole the parts they'd be in jail in no time.

What they do is merely copyright infringe - if that.
Launching soon: InvoiceDB – Automate your accounting
> I mean, yeah, I can toggle the light switch to get it to turn on, but then it gets screwed up and I need to go into the app to reset it when the internet comes back on.

That doesn't sound right. All the Zigbee/Z-Wave switches I use maintain proper state through HA, even if they lose connectivity for a period of time.
I wanted to get my data out of ask.fm because I answered quite a lot of questions there back when it was fun. The GDPR export option was nowhere to be found. Opened a support ticket, they asked me for a EU ID... Well, yeah, I don't have one, I'm not a EU resident, I wanted to piggyback on the laws of countries that actually care about their people. But it just struck me that they hate their users this much. Even Facebook didn't go this low.

On an absolutely unrelated note, I reverse engineered ask.fm's client API back when I was actually using it.
It has always been the case that API gateways implement a number of "nice to have" features around an API business but always omit the one feature you need to have an API business: payments.

My guess is that there's a kind of liability that could come out of being a payment gateway + other features in that situation (e.g. being caught up in a dispute between the customer and vendor) that is avoided when the service is not "batteries included".

It reminds me of the myoelectric sensor that you have to solder you own wires to (if you get a shock at least you're some nerd who soldered it on your own.) Or the idea that somebody would gather up your month's worth of medical bills, make sure they are right, pay them, add a processing fee (e.g. maybe $10 on a $100 bill... possibly saving you that much in misbilling.) and then send you ONE bill.

Trouble is that if the "one" bill is $150,000 worth of cancer treatment they might find themselves in the health insurance business!
also treating this "incident" as a war act
“arithmetic mean” is well defined (“the average as we know it” is not a particular sensible phrase to use in a subthread where the point in debate is specifically whether the average refers to one specific thing.)

That doesn’t make the word salad sentence used later in the article— “the mean is the arithmetic average”(emphasis added)—make any sense. Were it “the average is the arithmetic mean” it would merely be wrong, but at least make sense (and it would be making the same incorrect point it was being cited to support), but flipping “mean” and “average” so it claims that the former is the “arithmetic” version of the latter goes beyond wrong into being a pile of words that are individually sensible but don’t mean anything, right or wrong, as assembled into a sentence.
If you are a startup, then such a law directly benefits you because you might want to convince users to migrate to your services. If the big established competitor of yours has to offer data exports, such a migration is made easier for you, enabling your startup to grow faster, and giving users the ability to enjoy more innovation in the market.
The button of betrayal is right there in the demo.

Your privacy is not safe with Mozilla. It requires the same level of distrust as other browser vendors, but at least with those vendors people already know. Mozilla luls people in to trusting them and then uses that trust to fund a business model that is specifically about collecting and uploading user data.
That will make a whole lot of business models out there not feasible. The result will be fewer free services (to put it differently, fewer services and fewer choices). If you don't pay for stuff with your data, you can't have it for free. Are we sure we want to use government regulations to impose this on consumers of services, from the top down? Instead of, say, letting them decide?

(Yes, of course it's an industry talking point. The best kind - one that's true and valid, and so far not effectively refuted).
This code is above average by the standards of academia I've dealt with. You've got comments announcing what each part of the code is doing, and there is only one copy of each script. Normally, you would expect to have multiple nested directories with various variations of the same code, plus multiple variations of each script with cryptic suffixes.
I wonder what obligations the Swiss lords have been neglecting. Perhaps the townsfolk could bill for absent services?

They are not peasants, as such things likely don't exist in modern Italy. So how can they owe anything?

The Swiss baron's descendants - are they still barons? Can they still hold a fief?

Perhaps the Swiss baron's lord can be convinced to levy a similar tax on them, and return the money to the town.

It's very interesting.
there's no such thing as king of italy.

and since the thing came up: there is no such thing as prince of italy either, nor princess or queen.

and by the way, the savoia line of blood isn't even legitimate as heir to the now-nonexistant throne.

the legitimate heirs would be the descendant of Aimone duke of Aosta, which nowadays have better things to do.
Yes, data scientists frequently are working alone and don't care about readability so much as results. Also the code isn't going into production so they don't care about optimizing it by and large.
And get some motion detectors. Your lights should come on when someone enters the room and the light is below a threshold. I usually hit the off switch by the door when I leave, otherwise if no one is present the lack of movement will dim and then turn the lights off. It's 2021 people!
What else do you think people ought to do with them? They're pretty small, so e.g. reading a book is a bit difficult, and using them as general purpose computers is difficult because they lack a keyboard (and thus an easy way to program them).
I agree.

I've been considering trying to replicate magit in a tui. I'm not sure if I should go for a straight port (many people might find useful, eventually) or change lots of things to make it fit my workflow (might be more likely to "finish" if I optimized for me).

My dream git workflow is rebase-first, i.e. you have multiple WIP commits at any given time, and can send an unstaged hunk to any of them with the same level of complexity.
it's ok

there's dont be evil
Absolutely. Service providers have a real incentive to implement _import_ functionality, since it means an opportunity for new users on the platform.

Since the incentives for the service providers line up with the users, I don't see a need for the government to regulate importing data.

Export is the exact opposite. The incentives for the service providers go directly against a user. After all, if the provider export a use's data, then then that user can just leave!