skysight-inc/HackerNews huggingface dataset:
An author is defined as someone that authors something and not someone that makes money out of something.

When the market can't compensate authorship per copy this does not mean the author cannot exist, but that authors will be compensated differently.

Do you seriously think that people would stop making music because they can't become millionaires? There's tons of people making a living playing on YouTube, filling the niche, and living off endorsments and side-selling of merch or lessons.
Probably going to catch some flak for this but if you're really building a software product by yourself you're going to want to pick whatever tech allows you to consistently throw yourself at the product. If you write something from scratch you'll be bogged down by boilerplate until you're bald from pulling your hair out. If the documentation is poor you'll waste days on simple problems or from waiting on a return email from support. In my view this is a personal not a technical problem when dealing with solo or small teams.
I've found that even as a user it is very useful to have a mental image of what the "data model" looks like, abstractly. This is more important than knowing about all the features of an application.

I'm thinking user documentation should start with a quick explanation of the data model, and from there describe the operations that can be performed on it.
I'm not sure this is a useful distinction. I'm sure you're correct for whatever definition of "template metaprogramming" you're using, but Rust does have a pretty powerful generics system. That gets you most of the way to what C++ templates are used for, albeit less cruftily IMO. Coming at it from a different side, if a C++ person asks you, "does Rust have templates?", you're likely to say "no, but it does have generics which let you do most of what you need templates for". It's definitely enough to let you write complicated, over-general code if you want to. So in an informal context like this, the difference between "template metaprogramming" and generics is probably not one you want to stand on, at least not for your whole argument. There's lots of better arguments to make even if you accept Animats' language.
Outsourcing companies and independent contractors are different problems. A tech company's cafeteria workers, janitors, etc. are employees of the outsourcing company that the tech company contracts with.
It's easy to understand once you get just how simplistic it is. The VP will deliver a dressing down if the company loses money and the blame can be placed on the director.

The cost of an outage is very easy to quantify (revenue per minute the system is down), and the probability that something will go wrong while applying the patch is also somewhat easy to predict, and usually greater than zero. The director will be blamed with certainty for the outage, since he approved it.

The cost of a security breach is difficult to quantify; it depends on what gets breached and how bad. Note here, I say breach, not vulnerability. Even if there is a known security vulnerability, it's not immediately obvious in all systems what the consequence will be; there may be other mitigations in place outside of software that reduce the potential damage, or there may be unknown vulnerabilities that are exploitable due to the known vulnerability that make would make a breach worse. The lack of certainty about the consequences means it's also possible for the director to avoid blame if the breach is minor ("how was I supposed to know that other team is still using MD5?"). If there is no breach, then there is nothing for the director to be blamed for.

Given that the director would like to avoid being dressed down, director will be more inclined to delay patching over possibly causing an outage, because the costs of an outage are easy to predict and he will take all blame for it. The breach may never happen and even if it does, it may cost him personally less than the outage.

If this still seems weird, it might be because you are someone who views patching as an easy thing to do, because you probably work for a software company. Software companies are used to managing changing software, and have all kinds of practices around minimizing the risks of doing so. Non-software companies typically find patching to be hard and costly because their core business is something else; changes can disturb the "something else."
In cryptography, we've had eprint.iacr.org for a while now and if you want your paper to get noticed, an eprint version will do more for you than a talk at a second-tier conference. Even at first-tier conferences like Crypto, people will sometimes have "eprint 20xx/yyy" on their last slide to encourage people to go and read the paper.

Peer review still has direct value, and peer reviewed publications on your CV have indirect value so the IACR conferences (and possibly Springer/LNCS) aren't going away any time soon. But everyone I know of in the field looks on eprint first when they actually want to read papers.
Random.democrat
Yes, Ubiquiti rules! You can get 25 km links with equipment cost under $500, including dishes and towers.
I wholeheartedly disagree; write more tools, more code; own your skills.
I remember my first 1 gig drive, it was a full height 5 1/4" external scsi, with the giant 50 pin cable. You could hear the seeks from other rooms.
What is the non-tech industry supposed to do?
No, and you don't understand the current scientific ecosystem. Researchers are paid for their work through salaries and grants, and therefore benefit from open access. Publishers are not. That's why PLOS must charge authors a fee.
Yeah, the data structures define the program. Both downwards towards the developer and upwards towards the user.
I've received a fair few suggestions on insights in the humanities which I'm currently writing up to add to the post. I considered some of the Scholastics but felt that they hadn't had an impact on modern thought in the same ways as most of the others (which is a relatively good proxy for "correctness", which is one component of being "great", which is a bad metric but I have to draw the line somewhere). Would you disagree?

Also, I agree that there are some amazing artistic achievements. To keep things concise, I wasn't focusing on them here (I'll make that explicit now).
As far as I can see (and comparing with the output on the github page), the only
thing missing from dmesg is the amount of cache and byte order within the first 20 or so lines.

Well, yes. A subset of the information and interspersed among unrelated log entries as I stated.

One depends on CPU purchase, the other depends on the ISA. Either way, they're not something
I can do anything about even if I need to know them - which, most of the time, I don't.

Great!

I'd argue that the reason you think lscpu is predictable and concise is that you're used to reading it.

Actually, I've rarely used that command (probably a handful of times in the past 5 years) so you're about as wrong as you can get when it comes to using the familiarity argument. :)

I actually based my statement on:

lscpu -> gives CPU information
less dmesg.boot -> contains CPU information mixed in with other log entries

lscpu is more concise than the dmesg.boot log file

lscpu -> fields have fixed fieldnames
less dmesg.boot -> unstructured log entries

lscpu has predictable output compared to the dmesg.boot log file

In my world parsing output from command line tools that use predictable identifiers in their output is easier than parsing similar data out of unstructured logs.
Rule 6 is a corollary of "Every principle, and every group or movement based on a principle, eventually becomes its own opposite."
I think people who come to Go from not so productive languages might feel productive in Go. I mostly feel very unproductive with Go, like I'm wasting too much time dealing with code, when I should be thinking about the problem I'm solving. Although I almost completely stopped using Go at this point.
Good form is for every day people, it's not for people behaving like massive fucking bellends.
> It's only a common interpretation if you believe the rumors about Apple's view

Why do you keep talking about rumors? And why do you keep talking as if this is somehow unique to Apple? I'm pretty sure Apple's not the only company that believes this. In fact, I have no idea why the FSF would even claim otherwise; Apple's interpretation seems to be perfectly in line with the entire point of the anti-TiVoization clause.

If Apple were to accidentally ship GPLv3 software on iOS 11, under whatever interpretation you subscribe to, how is Apple supposed to remain in compliance with GPLv3 without releasing their root signing keys? Remember, we're talking about shipping this on existing devices, not on some hypothetical future device where they can add extra user-swappable keys to the bootloader.

You keep insisting that Apple's interpretation is wrong, but you haven't provided any alternative interpretation.

> If you want to start claiming that it's a "common interpretation" you need to show that there is a larger community than the Linux community that uses the GPLv3

That's a catch-22. There isn't a larger community because GPLv3 is toxic to companies. Nobody else is going to create a larger ecosystem of GPLv3 code because doing so basically means turning into Linux.
Ubisoft Montreal took on a lot of funding and received an office space too from QC provincial government.

In return they produced a ton of hits, Rainbow Six, Splinter Cell, Ghost Recon, Prince of Persia, Donald Duck's Goin' Quackers
- CRISPR/Cas9, CRISPR/Cpf1

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

Cas9:

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

CRISPR/Cpf1:

https://en.wikipedia.org/wiki/CRISPR/Cpf1

- Tissue Nanotransfection

https://en.wikipedia.org/wiki/Tissue_nanotransfection
Yes, those are a great place to start, but after wearing silicone tri-tip earplugs for about five years, I sprang for in-ear molds. tri-tips are more than good enough to block out noise, but they're much less comfortable, especially if you wear them for hours on end.

If they aren't comfortable enough for you to wear all day, it's not that expensive. I mean, some people pay about that much for a keyboard, and a good desk chair is far more expensive.

That said... thank you for sharing that store! More people should know about musician's earplugs and enjoy live music without tinnitus.
Huh, I have never known anyone to want spaces in Chinese or Japanese. I have studied Japanese for quite a while and I've never missed spaces; and although I've not really learned much Chinese, the thought has never crossed my mind when reading what little I can.

Ask even a native, and they'll tell you that characters are a big part of the problem (though less of a problem in Chinese than in Japanese).
Ask HN: What are evergreen Computer Science papers everyone should read?
You aren't meant to pay the $30, you're meant to be inside the firewall at an institution.
I'd say "a modification to the code designed to speed up that section of code". Are there other reasonable definitions? I thought it was pretty clear that the rule could be accurately paraphrased as "Don't optimize a section for speed until you're sure that's where it's needed."
The Minskytron: early graphics demos on an in-browser PDP-1 emulator
It's a transition that will take a couple of decades at least. People and transportation companies are not all going to run out and replace their cars and trucks with EVs in the next few years.

The same thing will happen with the demand for oil that happened with the demand for horses and carriages. People will find other things to do.
An unusual way to be screwed by illegal immigration but not a surprising one.
Reminds of what the people of Red lang are trying to achieve: http://www.red-lang.org/p/about.html?m=1

Maybe I'll finally give it a try!

Every once in a while I daydream about a sort of "distributed app platform" built on top of Scheme and IPFS. -- Perhaps Red would actually be perfect for this...
I really don't like my software to scream for my attention all the time. I'm looking at you Facebook, Google.
Show HN: Smart and fast watermarking for photographers
Get some Ubiquiti Bullet M[0] and parabolic dishes[1]. The Bullet comes with decent software. Setting up linked networks is pretty trivial.

0) https://dl.ubnt.com/datasheets/bulletm/bm_ds_web.pdf

1) https://www.amazon.com/Antenna-World-G2424-Directional-Parab...
> You can look at additional measures, not just amplitude. Packet type, for example. Or components of TCP conversations

Yes, I did that too. Had to analyze traffic to QA a VPN app.

> But Tor-specific parameters are buried in encrypted payloads, so amplitude is decent enough.

Indeed it is. It's even possible to do traffic shape fingerprinting on that.
Of course there are ways to beat the lottery. For one, ask the clerk which ticket to buy. They will gladly give you the one most people win from.

Also you can study the patterns. If you buy the same ticket over and over, a streak of losing is a good idea that something big is coming (uneven distribution of the odds). Most people at this point would give up and buy a different ticket, but that's a bad strategy. A streak of winning small amounts is actually bad (proper distribution of the odds). With a little social engineering (small talks with other customers), you can gather that intelligence. Evidence of this effect: the powerball, mega millions, etc. When no one wins they balloon. When someone wins each time, they win relatively small amounts.

Another mistake people make is buying different tickets instead of the same. That's why only a few people win.

So much of lottery is reverse psychology.
Why not Java, Kotlin, Scala, Clojure, C#, F#, OCaml, CL, Scheme, Haskell, or any other efficient GC language?

Its funny to compare Rust, whose sole purpose was to enable garbage collector free semantics, designed to reimplement an efficient and small memory web browser to languages with a GC.

Go is great, because compared to most other GC languages, it has small self contained binaries and comes with a great toolchain. Its AOT is better then C# and Java, and bundles its runtime with every app. It's not great, because people would really just want a more expressive language that had those same qualities. That's why there's effort for Kotlin native and Scala native.

If anything, the fact that some people are thinking to pick Rust over Go is a testament to Rust. Rust should have nothing of interest over Go, except for no GC. But apparently, even with the added complexity of a borrow checker, it has enough to entice people from GC languages.
> Every once in a while I daydream about a sort of "distributed app platform"

Have a peek at dat and beaker browser, they've done interesting stuff in that regard recently.
>modern power supplies and motors rely on the ever more powerful and cheap power transistors that we have these days -- they are able to switch power on and off at very high frequencies and thus reduce the size of the rest of the circuitry needed to raise or lower voltage. but this often results in extremely high pitched sound coming from parts that, for whatever reason, physically move or expand in response to current or voltage changes. in cheap electronics, this effect is not accounted for and controlled with vibration dampening materials applied to the vibrating parts, and the result is a maddening high pitched squeal.

Battery-powered motors almost always operate in the range of 80 to several hundred kHz, which is basically unavoidable. Those make up a minority of motors in your home. Wall-plugged motors use AC, in which case they have no high-frequency harmonics, or they are DC in which case the ultrasonic noise comes from the brushes scraping and arcing on the commutator. This is the source of noise in vacuums and the one you're most likely to hear but it's basically static at a very high frequency. Supposedly this is one of the reasons pets hate vacuums, because it's a loud noise of a rarely-heard pitch. Vacuums will be much louder than almost any other motor in your house.

The difference between cheap an expensive power supplies is often down to the use of fully integrated PSUs. The expensive ones operate in the MHz, which lets them use very small capacitors that are built into the chip. Cheaper supplies operate at closer to audible frequency, but they aren't actually louder despite using larger components. The efficiency is relatively close to a more expensive supply so the amount of energy loss is also similar.

>ive been meaning to buy something that will let me detect ultrasonic sound so that i can smash those devices with a hammer.

It's actually very easy to make one! Cheap (<50 cents) electret microphones can hear up to 100 kHz and are pretty common in DIY bat detecting microphones[1]. Note that you can't use normal ultrasonic sensors like those used in rangefinders (about 1 cm wide, black plastic cylinders). Those are heavily tuned to resonate at 40 kHz and can't pick up sound outside that range at all.

>ive always wondered what it would be like if you used a dual motor system in a car, where one motor is wound and sized for very high torque and the other motor is wound and sized for very high speed.

That's exactly why 4wd Tesla models have a longer EPA rated range, or at least speculated to be why, anyway. The EPA range test is done at a set speed and Tesla optimized on that by having one motor for lower speed and one for higher speed. It's also useful for vectoring torque to the front/back for braking/acceleration. You can't use it like a variable transmission though, since there's very limited benefit to splitting the power up.

The benefit in practice is pretty unclear since you won't be driving the exact speed it's optimized for and the difference in efficiency is only a few percent anyway.

[1]: http://www.wildlife-sound.org/equipment/technote/micdesigns/...
I am very much in favor of open access, but there is one service that these publishers could definitely provide that would definitely be a value-add: replication. I can imagine a prestigious journal or publisher using the money they've collected to sponsor studies that replicate results. I need to think more on how this model could work such that piracy doesn't circumvent it, but I think there is definitely a need for more replication studies and prestigious publishers have an incentive to ensure that their studies are replicable.
The article is filtered through another reporter and I didn't find specific instance of badmouthing (but my reading is also filtered through my own notion of where I think Alan Kay is coming from.)

If you're interested in what Kay really means, maybe listen to some of his numerous other talks?
Are you joking?

Women earned the right to vote in 1919; women have been historically oppressed in at least that sense for more than half of the lifetime of the US. Women are still considered property of their fathers and husbands in many parts of the world.
You guys are making me feel old. My father bought my first 20 MiB hard drive used for close to $1000. It was the size of a VCR and sounded like a jet engine.
In short:

Supply = Very limited.

Demand = Increased and ever increasing.

Result = $$$$$
I was this close to writing project Amy[0] with f# on .net core. Was an interesting challenge. But I snapped out of it and am usong django (something Im productive with). Day and night difference that is already producing results even though its about 50% done.

[0] https://github.com/yelluw/amy

It powers http://yelluw.com
(https incoming this week)
Is it a move from IBM to sidestep Oracle ? (I have no idea, just asking)
Edit: Yes I do mean 10MB!

Oh, I believe you. I say that because I was skimming to see if anyone could "beat" me. You tied. :-) And the only reason I was skimming was to comment to parent, who said they thought they'd never fill a 13Gb drive: yeah, that's what I thought when I bought a 10Mb drive 30 years ago.

Now, I don't think you can even buy media that small. Hell, the internet is infested with single web pages that wouldn't fit on that drive.
To be honest, its not a great article. I'll try to find a better one.
This was the 90's. They were 21" Sun CRT monitors, but spaced far enough apart (and staggered on either side of the table, if I remember right), that you could see enough of the person across from you to be distracting to me. There were 4 workstations on each side of the table.

They were close enough together, however, that the power-on degaussing coil would induct into the neighboring monitor, causing a chain reaction down the entire table.
In recent months I've been researching and deciding on what my "next gen" stack is going to be.

What would your stack consist of if you were starting a new project today?
Good lord this is an outstanding comment
TBH I don't really think there's a market in mobile apps. They're expensive and most groups don't see the need for an app.

If you find a group that needs an app then you've got your niche. Anything that requires daily interaction or that needs to use the unique features of a phone/tablet
Which ones? Note that an item being on the list doesn't mean it's a comparable achievement to all others on the list, just that it's above an implicit and slightly vague threshold.
Nikola Tesla > AC (alternating current) and the induction motor:

https://en.wikipedia.org/wiki/Nikola_Tesla#AC_and_the_induct...

Induction motor:

https://en.wikipedia.org/wiki/Induction_motor
The interface is the same. For example, in C# you have an interface Collection, which offers a lookup method, and which both HashSet and Lists implement.

The point of the OP is that among different implementations for the same interface, choose the simplest one unless you have empirical evidence that compels you to do otherwise.
Most likely. All those effects are already built-in, and it looks like there's a pretty comprehensive modding community.

There might not be an API callable from outside the app, though...
Sure, artists can now sell lessons, but that's not necessarily better than the publisher model.

How do you think your analogy would apply to scientific publishing?
> But that says nothing about the preferences of others.

That was exactly my point. OP claimed that it seemed like people on HN weren't using it based on the comments to this thread so far.

I'm claiming the opposite, that a majority of HN users are also relatively happy Facebook users, but that those users won't comment on threads like this. Because these threads always attracts the contrarians and turn into a pissing contest about who deleted their FB account first.
Did you get screenshots?