skysight-inc/HackerNews huggingface dataset:
The whole "users don't care" is really ignoring consumer's cognitive dissonance on security.

Adopting the stance that "vast majority of potential consumers in the world don't choose digital products based on security" time-and-time again bites organizations in the ass when there's a breach.
Covid-Net Open Source Initiative
It’s the infinite quarantine argument. Nobody will get immune and the vaccine/cure is years into the future, so we all better stay at home forever while the government takes money out of the infinite supply so we can order food that’s not processed in all these factories that are closed.
The usage of "1 to 1" in "`map` is a 1 to 1 operation … meaning one input produces one output" is at odds with the usual mathematical usage of the term; I'm not sure how it accords with CS usage. In fact, it seems to be referring to the `f` in `map f`, not to `map` itself. In mathematics, we say that an `f` that produces one output for one input is a function. (More generally one might consider non-function objects `f` called relations, often written infix as `x f y`; for example, we could have the relation `f = lt`, for which, say, both `1 lt 2` and `1 lt 3` hold—one input with two (or more) outputs.) If we say further of a function (or more generally of a relation) that it is one to one, we mean that different outputs produce different outputs.

For example, properly speaking, one should not speak of the square-root function, since there are two real square roots of every positive real number. (What we usually call the square-root function is really the non-negative square-root function on non-negative reals.) There is a perfectly good squaring function, since every real number has a unique square, but it's not 1 to 1 on the domain of all real numbers, because different real numbers can have the same square.
I tried, but your email server is down! Gmail is saying it's timing out.
It's probably reasonable to assume that half the attendees at DEFCON can use that backdoor. There are several known vulnerabilities listed in the linked Wikipedia article which have to be patched with a firmware update that some OEMs didn't bother to provide and most users didn't bother to install.
You're missing the point, too.

Tracking isn't the hard part.

Documenting "what to track and what it should be" UP FRONT is the really hard part.

The goal is to set things up so that when your system scans a QR code for that barrel of "reactor cleaning fluid" and it scans as methanol instead of ethanol the system starts screaming at you.

You can do all the steps by hand with a paper register. Nobody cares what your recording substrate is. However, they do care that it gets recorded in such a way that it can be verified.

And I would say "Someone has a problem and thinks "Oh, I'll use blockchain." Now he has 2 problems."
Go is the golden standard for extracting the most value out of unexperienced computer science grads but it is not the measuring stick, not by a long shot.
Santafe institute's 'Introduction to Complexity' online course uses NetLogo to run simulations.
I believe users won't care until it's common for there to be repercussions from not caring. If not caring means my odds of having my savings account stolen are %20 a year then people would start caring. As it is there are few directly attributable repercussions. Just vague worries about future problems.

As it is what are the odds of any one user running into issues because of lack of security and privacy? It seems fairly low.

It seems like an opportunity for Apple (assuming they're actually better) to run some scare ads (99% of people scammed via there computer were running Windows/Android) if that's true. If it was true a good ad campaign could get people to care?

For internet stuff how about 98% of the people who got their bank accounts hacked were hacked by leaks of data on Facebook. (probably not true and not provable)

Maybe we need some security insurance who will then audit software and only insure customers that use certified software? They'd have an incentive for their audits to be good because they pay out if it turns out the software is not secure And if their market was big enough then software creators would want to be certified.

It's even possible some standard sandboxes could help make it easy to certify. Add this sandbox to your app and you're certified? Maybe some OSes that already have sandboxes would automatically get certified but server side you'd need audits?

Just throwing out ideas.
> the cost of extracting oil is so high in Iran in particular

I don't think this is the case. I think it's "balance the country's budget", not the break even point in oil.

Wikipedia has a 2016 table of extraction costs, which shows Iran is only marginally more expensive to extract than Saudi Arabia: https://en.wikipedia.org/wiki/Price_of_oil#Comparative_cost_...
As long as the old thing works there is no reason to chase the new features, especially because they are by definition not available in old browsers.
I guess google has old data ;)
Tim Dodd just released an excellent (and long) video comparing the costs of SLS with Falcon Heavy and (eventually, maybe) Starship. https://www.youtube.com/watch?v=KA69Oh3_obY&feature=youtu.be

SLS will cost upwards of a billion per launch. Compare that to $90 million for a reusable Falcon Heavy launch or ~$150 million for a disposable one.
I agree, at some point we're going to get regulated into a painful place
Actual practice: the journalists stick in a magic word, they're indemnified, everyone notices they use the magic word when it's obviously true and also when it's not obvious and so assumes it's just a legal device.
Hi! This is really great. Quick feedback for.minor improvements:

General:

* Maybe 1-2 sentences more at the beginning for what appears at the end ("web app that runs in your browser") and what is the use case (for where your servers can enter the info and it appears at the bar?)
* Some kind of customer/table identifier would be useful?
* Quick instructions at the end how to use it. E.g. "both bar and server open the app on their phone"

If your target audience is really non-tech people I imagine they might struggle with the instructions for

* step 5 (just spell it out a bit more)
* Step 8 and 9 (mention where to find those settings)
* Step 10 onwards: suddenly you mention software that was not yet introduced and there are a few terms that dont make sense unless you understand them already
* Step 11 - something is missing: what do I do with the code I've changed?
* step 12 is a bit quick and I'm not sure what comes out at the end. E.g. where to click "run the app" and where it will appear

Hope this helps, really well done and this is just nitpicking ;)
Asking someone who took their last (undergraduate) architecture course more than a decade ago: Is it possible to design a motherboard that will shield the user against Intel ME / AMD PSP-induced shadiness? Would it be possible to do this without performance impact?
Your first language is hard because you're learning a ton of things all at once, only one of which is the language itself.

Your second language is hard because it's not the first, even though it's probably pretty similar. But the differences will catch you out. A second language challenges the mental models you built up with the first language -- you have to tear some of your understanding down and come up with a more generalized perspective.

Languages similar to the first two become easier to pick up after this point, because you're mostly looking for a handful of differences, not a total paradigm shift. But languages that are sufficiently different, like C and Haskell, require a lot more of the ground-up type of work you thought you'd left behind by now.

It gets easier and easier as you cover more of the conceptual landscape. But I'd be willing to bet that many developers haven't had to journey far from home.
Again, what can I say? I wrote my stripe code over three years ago so I don't recall many of the details. All I know is that I don't recall having any trouble with it.
Exactly, this is where the strength in numbers and economical power of the EU comes into play. EU commisions should contact the Russian foregin ministry and demand a full response immidiately.
I find the opposite is true. Learning the first programming language was hard, the second was easier, the third and fourth easier still. At some point you develop intuition about what computers can and cannot do in a universal sense and then you realize every language is just different nuances and emphases on those capabilities, and it becomes pretty easy to pick up a new one very quickly.

Edit: after reading the paper I understand the emphasis is on conceptual mistakes people make when coming from one language into another - you assume things work like A and make mistakes when B works differently under the hood and you don’t realize it until banging your head against it for a while.

That experience does ring true, but I stand by my original comment, this is mostly only an issue for language #2, and with each language it gets easier as you begin to think more in universal terms and have fewer assumptions and gaps where you’ve been accustomed to something that “just works” in the environment you’re most familiar with.
2 points:

1) The blog touches on it, but can you imagine the temptation of shady (and non-shady) companies out there to try to engineer a cheaper version or to cut corners to gain some of the margins charged for such a seemingly-simple piece of hardware?

2) Do you remember 20 years ago, 5-10VDC power supplies for computers used to be this gigantic ugly black brick with cooling fins that weighed 2 pounds and had embarrassing Apollo-style connector plugs? Amazing what miniaturization has achieved.
How to Set Up a CI/CD Pipeline for a Node.js App with GitHub Actions
I had to rebuild a raidz+1 last year.
Went OK, except the replacement disk turns out to be an SMR disk...
The rebuild took almost 2 weeks.
> I think you're extremely confused

I think you missed the irony in it.

You're not wrong about the 2nd point, it's part of what makes it effective; be oblivious and you'll believe everything or be cynical and believe nothing.

(And yes I edit my comments for typos, rewordings or when I think I was uncharitable regarding the original comment)
I think it only works for older versions of IME.
Or NixOS/Guix, which treat the system as immutable (ie. in Nix pretty much everything but the Nix store at /nix is built after boot anyway). Or macOS by using a read-only system volume.

The grandparent bug is as much a failing of the grandparent's script as the OS, which exposes itself as one global mutable namespace.
Media Server Manager
> the portion of white students who are legacy admits

I’m curious to learn more about this. Do you have a good source for this data?
Why is that a problem? Most of the data types have mutable and immutable variants. buffer -> string, table -> struct, array -> tuple. The mutable variants have a `@`.

https://janet-lang.org/docs/syntax.html
Title is a little misleading as it seems to imply that programmers find it difficult to learn another language. But there is no such implication in the study. The study really seems to be about specific language features that can contribute to making it harder/easier to pick up.
I am experienced software engineer. I want to start learning AI, do you recommend any articles books, and order in which I need to proceed.
I agree with you. I think there are some problems with the study. For example "Does cross language interference occur?" Not only does it occur, but that's literally how you learn a new language. You make assumptions based on the languages you know. You write code. You notice that it doesn't work the way you expect. You try to understand what is different. It's by far the fastest way to learn a language rather than a problem.

The learning strategies of successful language learners show this: Learning on their own, Just in time learning, Relating new language to old langue. I would say that the "Language interferences" are just a product of the learning method. Putting yourself in the deep end and trying to swim always results in a little water in you lungs ;-)

The fact that it is challenging does not imply that it isn't desired. In fact there is a whole branch of skill acquisition theory called "desirable difficulties". While I think their theories of what would make the process better are interesting, I don't actually agree with their conclusion - that we should proceed as if their theories are correct.
Perhaps some setting where you can make it impossible to reply to a comment or thread would help. Some people will never accept that in the end the only right they have on a forum owned by someone else is to leave.
I thought this was going to be a story about making a simple application with a deliberate limitation. Like a feature.
I’d agree that similar languages are easier to learn, but once you’ve learned how to learn a programming language, new ones are easier, even if they’re dissimilar from your prior languages.

For the record, my professional work includes languages as dissimilar as PHP, Java, and Common Lisp, while my hobby hour work includes Rust and Haskell. That’s a pretty wide range of the language space that exists today, IMO.
Precisely: it encourages the reader to make the judgement about what appears obvious.
Are Anker chargers engineered well enough to match?
> And "medical monitoring" doesn't mean it won't kill you, it only means if you die they write it down.

I think perhaps you've never run a clinical trial. What's involved is far beyond what you are describing.
Israel resorts turns to Cannabis in Coronavirus treatment
The connection between CF and Covid-19
You are misunderstanding my point. My issue isn't with the individuals, my issue was with the war time "stories" made up by the military/news.

Pat Tillman was killed in friendly fire. But the story we got initially was that he was killed by the enemy.

"Lieutenant General Stanley McChrystal approved the Silver Star citation on April 28, 2004, which gave a detailed account of Tillman's death including the phrase "in the line of devastating enemy fire," but the next day he sent a P4 confidential memo warning senior government members that Tillman might actually have been killed by friendly fire"

https://en.wikipedia.org/wiki/Pat_Tillman#Surrounding_Tillma...

Certainly Tillman didn't spread the lies. Jessica Lynch didn't spread the lies either. It was the military/news/etc.

Hence : The first casualty of war is the truth.

> Full disclouse: I knew him personally… mostly from a distance.

Yeah, I knew him "personally" too like millions of other football fans.
I've had systems become unbootable, services not start, that sort of thing. All perfectly understandable bugs that have been fixed, I'm sure, but fundamentally my experience is that it's this intrusive thing that I never asked for that's broken a bunch of stuff that was working fine before.
> We need to use a full five-part response to end the pandemic: social distancing, contact tracing, testing, isolation, and treatment.

This is the US - we don't do any of those.
You have smartphones uploading location data and browser history every day for years and it almost goes unnoticed.
Here’s a bigclive tear down of an IKEA KOPPLA USB power supply, it seemed well-built https://youtu.be/uRe9w5PKmsE
> Is this normal in the USA? Talking of "premium offerings" in the context of healthcare seems sickening to me.

The whole US healthcare system is sickening.

Just related to corona:

1) ventilators have been used not to help patients, but to protect staff from aerosolization. The problem is that intubating and drugging somebody causes serious health problems in itself.

2) various hospitals and doctors are adding corona as a cause or factor to increase billings, whether it's related to corona or not.
Hard to know if it's universal or just all the language designers being influenced by the same stuff.
> How's the regulatory oversight in China?

lol. I think you're missing the point. The only "oversight" is that the CCP gets what they want, or else.
I feel like we'd all be better off if the federal government just cut an equivalent no-strings-attached check to Alabama in perpetuity, cancelled the SLS, and freed up all the rocket scientists to build something useful.

They could probably even do it in Alabama! SpaceX could open a local branch and mop up the talent. The current "waste money on the SLS for political reasons" just feels like the worst of all possible worlds.
I find the replies super racist. Maybe I'm missing something

wooflie says "Americans always smile.". Americans is a super set of "Asian Americans". If you're comparing to Asians from Asia then your reply is irrelevant, the topic is not about foreign Asians. If you're not then your statement " Americans always smile." is basically implying that "Asian Americans" are not actually "Americans"

"Coffeeling" says "Whenever our American boss comes to visit this side of the pond". What does "this side of the pond" have to do with anything? The topic is about "Asian Americans" so same side of the pond.

"billfruit" says "Chinese American's may be exposed to the Confucian thought". So what? So might a white American or a Black American. There's more cultural difference between a white person from New Orleans vs Santa Monica than there is between an Asian American growing up in Cleveland and a European American growing up in Cleveland.
How is this implemented on iOS where the operating system doesn’t allow apps to do this?
Daniel Pearl's parents challenge freeing of his convicted killers
Top Ten Best Electric Bass Guitar – Amazon Product Review
Compared to $1m for a reusable Raptor that has more power at sea level.

There really should be painful monetary and career consequences for the people who makes these insane decisions. The reality is it doesn't matter a bit and they'll retire with a wall full of accolades.
Sure, which is exactly why I said I'd expect at least an occasional update to a readme to say the framework has been tested and still works.

More broadly for web dev though, the fact a feature isn't available in old browsers is a bad a reason not to use a new feature if it's useful and improves a site for the user. Obviously you shouldn't break your site in old browsers but progressively enhancing to take advantage of things is a very good thing. Browsers implemented @supports in CSS for precisely this reason.
Looks like good ol’ screen diffing. It may be possible to use heuristics to detect when a rule might be important for layout in other configurations but this is probably good enough for the stated purpose of highlighting what CSS is important for learning.
Yes, for much the same reasons. Pretty much any ML-family language has the same effect; just having proper sum types, polymorphism and first class functions (and not having null) goes a long way to preventing huge classes of bugs.
Textpattern is a bit like "everything that's modern and hip right now, like SSG, let's do the opposite".

It got a lot of attention and love back in the day, because everything is in the database. No template files or anything. You just backup your database.

(It would be great if SQLite was officially supported, or anything but MySQL)

It has a large (for the time) ecosystem of plugins. Which are base64-encoded strings that you upload in a web form in the admin interface. The horror, I know! But back then it was seriously cool.

All templates, forms etc in the database also means you don't have a file lying around. Which means you cannot point your favorite text editor you it. You either use the builtin "editor" (just a form field) or copy and paste it into your editor and back, if you need syntax highlighting, validation or whatever.

Textpattern was pretty much dead a few years ago, but then development picked up again, and now you get a new release every now and then. The development team finally made XHTML optional and HTML5 possible (already quite some time ago), they expanded the builtin template language with new tags. It's tasteful development, not hectic.

Textpattern is great! I'm thinking about using it for a new project as a quasi-SSG, building my site and then wgetting it into static files.
As if "data science" would be a field where the full scope of SQL is covered. SQL was developed for the enterprise world.
I found this talk pretty interesting. Thankfully, the speaker doesn't limit the talk to "starting the debate," one of the world's annoying rhetorical tricks. She actually comes out in favor of an identifiable, different pedagogical method, and is doing research to establish whether or not it is superior.
what do you think is a better tool to specify and parse languages?

That's unfortunately an open problem. As I mentioned here, lexing is "solved" but parsing isn't:

https://github.com/oilshell/oil/wiki/Why-Lexing-and-Parsing-...

Here are what some recent languages do:

Go: Maintain a written spec [1], with multiple hand-written parsers. (I think the main one is in Go, while gccgo has one in C++?) I believe Go used to be parsed with yacc, but they moved to a hand-written parser for error messages. It looks like [2] was an early attempt to keep it generated.

[1] https://golang.org/ref/spec

[2] https://research.swtch.com/yyerror

-----

Rust: The parser is hand-written, like Go. There's a grammar in the spec, but like Go's, it's not used to generate code, so it isn't tested. They also have an LALR(1) grammar which was suppoed to be an executable specification, but as far as I can tell that effort has not made progress recently.

It used to be done with GNU yacc but it looks like they moved to a Rust-based tool [3]

[1] https://doc.rust-lang.org/grammar.html

[2] https://github.com/rust-lang/lang-team/tree/master/working-g...

[3] https://github.com/rust-lang/wg-grammar/tree/master/grammar

-----

So basically the state of the art is fairly laborious. It's basically write down the grammar, implement it by hand, and try not to make any mistakes. If you need to implement it again, which is extremely common (e.g. for gccgo, for Rust's language server), also try not to make any mistakes.

When you need to change the language, update the spec, and change all the parsers by hand.

I've written multiple recursive-descent parsers based on grammars, and it's not hard if you have examples to test with, but mistakes can easily creep in.

Rely on users to report bugs. There is a "long tail" of programs that will tickle various corner cases.

-----

Here's the approach I took with Oil:

How to Parse Shell Like a Programming Language http://www.oilshell.org/blog/2019/02/07.html

which is basically to do as much work as possible in the lexer, use a high-level programming language translated to C++ for the parser, and to use a DSL for specifying the AST. This approach keeps the mistakes and tedium down because shell is an extremely large language syntactically. (It could be the biggest of any language except for perhaps Perl. Shell is relatively small semantically, but huge syntactically (which is why I'm preoccupied with parsing :) ).
I wondered about that, since the original document obviously was a pdf. Anyways, doesn't matter because your fork did the right thing for me on 24" @1920x1200, while i've been up for about 7 hours, reading and beginning to feel a little tired.
When i came across your's it eased me into focus. Again: This is how it should be!
That’s not a secret, it’s pretty well known. It only takes one person to notice.