skysight-inc/HackerNews huggingface dataset:
The process for inclusion of most modern emoji is the exception, not the rule. That exceptional process isn’t one you can get in on as an individual, either. It goes like this:

1. Some large-userbase OS+messaging services provider, like Apple or Microsoft, sends a “proposal” for some new codepoints to the Unicode Consortium. The explicit message is “do you think these are worth standardizing?” But the implicit message is more unilateral: “we’re giving you advance notice, that we’re planning on including this emoji in our fonts + supporting it in our messengers, whether you like it or not, and whether it’s inter-compatible with anyone else’s systems or not. If you don’t standardize it, we’ll encode it using the Private-Use Area.”

2. Given the Unicode Consortium’s goal of never having proprietary text bits flying around the Internet — and given these big service providers’ histories of running messaging services (e.g. MSN Messenger) that did use proprietary encodings for emoji, resulting in some lasting problems with digital archaeology — the Unicode Consortium feel pressured by this “proposal” to standardize the proposed emoji codepoints, whether they really think they’re “worth” being standardized or not.

3. The Consortium also then feel pressured to get a new standard revision out quickly, to get ahead of the planned usage by these service-providers (because that usage would have to be encoded somehow, and if they don’t give the service-provider a codepoint to use by the time they ship their new font version that includes the relevant emoji, they’ll just have to make up their own.) In most cases, the Unicode Consortium is reactive to existing usage, allowing them to judge whether there is real existing adoption of a symbol; but here, they have to be proactive, pushing out a standard that includes a codepoint before knowing whether anyone will use it.

As a result, you’ll see these large dumps of new emoji where Apple/Microsoft/Google/etc. just decided autocratically that the world needed some more emoji, and Unicode begrudgingly followed along. It’s like what happened when Unicode first absorbed the emoji codepoints of Japanese feature-phones; but happening just-in-time, one at a time. (If those Japanese feature-phone manufacturers kept introducing new emoji, they’d have had to absorb those just-in-time too.)

There’s a separate, much more sensible and deliberate process the Unicode Consortium goes through you’re a regular-sized actor who’s not attempting to strong-arm them, where you do tend to have to prove existing use in either analogue documents, or as part of some proprietary digital text format.
Yeah, they've done experiments with patients with no long-term memory where they do things like shock them when they shake hands. People develop an aversion to it but can't explain why.
This is great. Thanks for sharing
I doubt Go will be used in the future more by several times than it is now. Looking at Google Trends, we're past peak Go, it's now on the decline:

https://trends.google.com/trends/explore?date=all&geo=US&q=%...

I haven't seen anything that would indicate anything else than Go slowly declining much like Ruby has. In other words, it's still around and getting new updates, but losing mindshare.
> During the test, the student is only working on the test, which is not private or secret.

You fail to consider the circumstances in which the test takes place. Students take the test in their personal spaces, and earlier in the thread, you mentioned essentially inspecting a student's living space (...angle of camera, light, checking environment, etc...) "Checking environment" is really just a cold, "process" word for inspecting a student's living space.

A student's room can often have private or secret things about them. Before you ask, not every student has the privilege to use a separate, clean, blank room to take tests. A personal space is inevitably going to have personal, private things. I've brought this up before; I personally know friends who were outed to professors as trans because their personal space has things like needles - and then you even have stuff like naive professors assuming "drugs" when its really just medications.

It could be anything else besides that, in fact - calendars with things scribbled on them; family photos; posters for political organizations; if you look in someone's bedroom, you're inevitably going to find out things about them that they would rather you not know.

Would you take your students on a tour of your bedroom while you're teaching an online class?

EDIT: In addition, there's non-traditional students and high risk students, and interruptions in general - there's not _only_ a test going on - I've had someone from my family interrupted in the middle of an exam because someone from the government knocked the door to take our temperatures and ensure we're healthy and don't have COVID. There's always more things going on, too.
from the title and the URL, I thought this was going to be which languages are the most and least energy efficient.
They are not copyrighted, they are trademarked by a nonprofit called GINETEX that licenses them freely, but with agreements that mandate their correct use.

They are not likely to want to give an open license to the public via unicode that might result in incorrect labeling.
A fitting Feynman quote:

A poet once said, 'The whole universe is in a glass of wine.' We will probably never know in what sense he meant it, for poets do not write to be understood.
I mean gnome 40 came out weeks ago. Not going to be in Ubuntu for a while. (Ubuntu does tend to lag on the Gnome front, which does give a chance for theme and extension devs to catch up)
Yeah, C# and Python are my two daily drivers. I think a good case can be made for C# due to excellent tooling and sitting in the sweet spot for statically typed languages: less enterprisey and more practical than Java and less painful than C++.
When I bought a 250K€ apartment in the Netherlands, my total cash outlay (down payment plus costs) was around 40K€. Anecdotal point supporting those pointing out that owning a 450K€ home in Europe is indeed still within reach for someone saving a modest amount each year.
I had not heard it called that before. I got 'slippery' from Ashley. His book is a gem but I imagine you know that :)
If your Rust program needs a more complicated configuration (conditionals, access to APIs and so on), also look at Facebook's Starlark parser and tooling[1]. Starlark is a subset of Python used by Bazel, Buck and a few other projects.

[1]: https://github.com/facebookexperimental/starlark-rust
Rust is already brown. I love it.
Or ask for 6 figures, especially for remote work and you can just work for Swiss or Silicon Valley companies.
A top 10 MBA program my partner went through had several people cheating in the program. I'll give you some anecdotal notes. Some cheaters get discovered and "outed" (esp those the group didn't like) when they brag during parties, some never gave up enough evidence to make an accusation official, others would talk about hiring CPAs for accounting exams/projects. Many in the class were concerned on whether normal study groups counted as cheating, as defined by the honor code!

A sibling program at the university exposed a cheating ring of ~15-20 people, and I think many were surprised that the result was to simply zero their grades for that class instead of more severe action.

/e I mention incidents and sizes since these programs are not thousands of students but tens or hundreds.
Doctor, Lawyer or a couple where both work full time and earn good salaries.
Indexes? Lol when has that happened and not rebound within a few months?
My intention wasn't to trash-talk, and I admitted my bias up front. I'm just speculating, and I think that speculation is legitimate and relevant to the subject at hand.

It's my belief that whatever difficulty there is around onboarding people into Rust (setting aside the question of exactly how much of a problem that actually is or isn't) is "constant", where the difficulty of onboarding people into a legacy codebase is, shall we say, "polynomial" over time. Rust adds some constant overhead in exchange for reducing that polynomial growth, and my belief is that at some point the larger polynomials outpace it, ending up with more total difficulty for newcomers to a given legacy codebase. Of course time will tell.
For most of history, in-person exams were possible.
Ah, that's fine.

Everybody will also pay for all the infrastructure you might be using and the others not.
Yeah I agree. I'm a bit mystified by the love for python. It is very clunky compared to ruby. I often wish ruby would have gone the scientific data route rather than the web services route, instead of python being the primary game in that town. But I am not at all mystified by people dreading rails.
Sure, but even if 100% of your users will be on a desktop site, you still need to deal with a browser window that has resized down to 300px.

At _some_ point, you will have to have a significant transition if you have an website that is mostly optimized for a desktop, full window experience.

I agree that many sites overdo the transition, but there are some things that really do warrant a phase-change at some point.
There is now a good parser/interpreter already written for a proper configuration DSL in Rust - https://github.com/facebookexperimental/starlark-rust
> I think it's great that Firefox is bundled with Ubuntu, but I have to manually update Firefox each time a new release comes out because the version that's installed is a canonical-controlled version that stays 'stuck' on a old version and doesn't have an auto-update mechanism.

This is par for the course on some distros. Fedora, for example, has its own repository for Firefox that is sometimes behind the mainline release of Firefox (although in my experience it's usually only a few days).

The advantage of the process is that the Fedora Firefox repo actually has its own QA testing, so they occasionally catch some things that might impact Fedora users specifically, that otherwise might go unnoticed if I were to switch to the Firefox flatpak.
I had to print this

https://tmuxcheatsheet.com/
I have two properties, still live at home with mum since I'm paying her rent and both my properties sit empty while the bank keeps taking money from a fully paid off mortgage.

Just like real life!
I think you have this backwards. Go is explicitly optimized for software engineering; in fact, it's the only language I'm aware of that makes large-scale engineering its north star. Here's Rob Pike discussing how Go's design decisions make building and maintaining large programs easier: https://talks.golang.org/2012/splash.article
(AFAICT, Rust was not named after "collecting Rust," and long-term maintenance is not one of its primary design goals.)

As an example, one celebrated feature of Go is that "all Go programs looks familiar," i.e. it's easier to get oriented in an unfamiliar Go codebase than just about any other mainstream language. Partly this is due to `gofmt`, but also the fact that the language itself is relatively spartan, with few dark corners. It's an "unsophisticated" language, which obviously cuts both ways.

Rust, by comparison, is a highly complex language. It allows for very powerful abstractions -- as well as very bespoke and "clever" constructs. I think Rust will develop a solid reputation for correctness, much like Haskell; Rust programs will run for many years without bugs or performance issues. But, again like Haskell, Rust will also have a reputation for allowing clever programmers to write too-clever code. That's why Go will prove to be the more maintainable language: because it intentionally limits expressiveness (a highly unpopular decision, unsurprisingly) and thereby limits the amount of "damage" any given programmer can do.
Signal saves lives too. No doubt certain users would be assassinated if their messages were intercepted.
I may have missed a line in the original text, but I don’t find what are the 5 loved brown languages.
I feel they may be the most interesting to learn, having passed the test of time and still being loved.
Flipdot Tetris [YouTube]
Supreme Court Cuts Federal Trade Commission Powers to Recover Ill-Gotten Gains
The Supreme Court on Thursday clipped the Federal Trade Commission’s longtime practice of seeking to recover ill-gotten gains in court from companies and individuals who cheat consumers, saying Congress hadn’t actually given the agency that power.

The court, in an opinion by Justice Stephen Breyer, ruled unanimously that a 1973 law, which gives the FTC the right to seek court injunctions against fraudulent or deceptive commercial activity, doesn’t explicitly give the commission the right to seek financial judgments as well.
And a "sanity-effective" alternative to Windows - I've found that running their officially-supported container has been a much better experience.
it's a pretty low risk gamble for the politicians and there's almost always a reward for them even if the deal falls through.
I'm thinking of a distinction between eg body of knowledge to mean the arrangement of muscle, skeleton and organs, versus a corpus of knowledge that you presume to be a representative collection of body parts making up a adequate whole.
I use it frequently too, but there's some terrible edge cases: https://stackoverflow.com/questions/53648244/specifying-the-...
I am under the impression that this more of the regular case in Greece. There is no need to threaten your manager, because the manager also would have a second job elsewhere.
It seems tautologically obvious, but I can elaborate anyway.

The benefits that led this project to choose an open source approach applies to other domains as well. If they believe in those merits, then they should naturally be apparent in the other systems that they would rely on, such as their collaboration tools. If you want the advantages of open source to proliferate, you have to cast your lot with more open source tools. They're equally suited to the task as, say, Discord.

Choosing proprietary tools and platforms can also easily serve to reduce your pool of potential contributors who don't want to use proprietary tools, and especially those who don't want to install proprietary software on their own computers, like the Discord client.

Some people simply cannot use something like Discord at all - it has a high hardware requirements floor, poor to mediocre Linux support and completely absent support for systems like BSD, not to mention grave accessibility problems. Only an open protocol enables anyone to build the clients that suit their needs, and are not dependent on the whims of some corporate board of director's determination of your merit (i.e. financial exploitability) as a participant.
I'm going to be the heretic and predict the opposite about Go and Rust. The reason is that Rust is overengineered, allows for macros, and is getting more and more complicated all the time. It's going to be as complicated as C++ in 10 years from now. Go is kept simple, the team is reluctant to introduce large changes, and it was from the beginning planned as an "easier C" with automatic memory management.

I'd also like to challenge the idea that Rust is optimized for maintaining. It's optimized for backwards compatibility. IMHO Ada is way better for long-term maintainability and in that respect beats every other language I know.
Weekly: yes, PWAs (progressive web apps) are not only the future, but the present.

Most every app you are using has a mobile-reactive webapp that'll invade your security + privacy less.

Microsoft has adopted this heavily. Outlook, for example, is now a cross platform PWA.
SQL is one of those languages that found its way outside of developer circles. My father-in-law knows SQL, and he's just about as far as you can get from your stereotypical developer. SQL is much easier than a lot of other languages, but it means people who have no experience with the ins-and-outs of software development are going to use it. These users are guaranteed to employ the language in ways that are not "proper" but instead ad-hoc and problematic.
Especially when the populational trends imply that demand for housing will go down on the distant future. Future performance is almost guaranteed to decouple from past performance at some point.
I haven't read much modern Russian poetry, but this really isn't that good. There are way better contemporary examples.
I guess things are 'interesting from the start' because of a coincidental state of mind when approaching the topic. Its emotional, not intellectual?

Engaging is pretty well understood. Its putting your full consistent attention on a task, and attempting to perform it better.

I find some things interesting at some point, and not interesting at others. The thing doesn't of course change. Its all me.
Not sure why you would expect people to act any differently when given freely reproducible content. The only solution here would be making adblock illegal and ramping up surveillance.
Rails is still the elephant in any web application room. But it isn't hype-y, it's just the mature option for its use case.
The "no"/"norwegian" thing is emblematic of very sloppy thinking in YAML's design, and it's far from the only example.

It's possible to avoid these pitfalls - like people do with PHP - but why burden users with that in a new project when better options have been available for years?

They obviously like Rust, why not just follow their lead with TOML?
Surrey computer scientist who claims he created Bitcoin launches legal action
If signal was lying, it would probably be easy to prove (at the very least the version of ffmpeg included is easy to prove/disorove. Ditto on the apple libraries).

Honestly, i would be very surprised if cellebrite didn't have massive vulns. Its the type of software that always does.
Anyone having issues with nextcloud client segfaulting after upgrading from 20.10 to 21.04? Running Xubuntu. Their latest AppImage seems to work though.
Firefox 90 removes GTK 2 dependency
Thanks for checking it out - we are using React. We made the design decision to go with Dark Mode off the bat. I see where you are coming from, we have had a few people mention that.
Non-welfare states also have infrastructure, so no worry about that.
Agreed, whether you rewrite or change in-place you're not going to be confident in the outcome unless you have tons of end to end tests first.

Then you need to find and skip/ignore the tests that don't actually test end-to-end behavior or business logic, just some implementation detail along the way.

Only then will you be free to do what is probably the first step if you have a crappy codebase: start establishing domain boundaries and interfaces and splitting things across those lines.
Have you exhausted all options for why prices will only increase?

I can see a scenario in which inflation rises and increased mortgage rates deflate the current overvalued housing market.
> an explanation for why Scala and Haskell are both loved and hated

I would posit it's unlikely that the same people both love and hate them. My guess would be we're seeing the OO-FP divide in action. If F# or Elm were more popular, they might be on both lists, too.

In fact, if you interpret it liberally, JavaScript might be considered FP by some takers of the poll, given browner JS codebases (pre-await) would need continuation-style approaches. Obviously, JS has other [reputation] problems, too.
Krebsonsecurity stories have examples all the time, if you don't want to click random links on Google/from people here.
Also pretty sure Ubuntu keeps a few old versions of Linux. And GRUB uses it's own ZFS module.
They just now found the tools to enforce it.
I'm confused. Zellij uses wasmer and wasmer-wasi. Wasmer may use cranelift for compilation (dont know if Zellij does).

"Fast & Safe. Wasmer runs WebAssembly at near-native speed in a fully sandboxed environment."
(https://github.com/wasmerio/wasmer)

But ...

"Cranelift does not yet perform mitigations for Specter or related security issues, though it may do so in the future." (https://github.com/bytecodealliance/wasmtime/tree/main/crane...)

Will the wasmer runtime handle specter / meltdown / rowhammer attacks?
However, Kindles can't read epub directly. If you're trying to produce a file you can sideload on your (or your customer's) Kindle without going through Amazon, you're still gonna need mobi, or one of the later proprietary (and undocumented) Amazon mobi variants.
Scripting languages can be great for very quick iterations, but they can also cause serious issues in larger, mature projects.
Good catch, I will update menu background and at some spacing for the leader section. Thanks!
don't do it. my experience, this is broken by default
I would prefer not to let Signal casually guide the press cycle's attention away from the fact that they're still planning on shipping a cryptocurrency grift to exploit end users. Don't forget that Signal is a corrupt organization.
Where do they mention in-browser use? WebAssembly is used for extensibility, but not necessarily for access from a browser.

Am I misreading their blog post?
> In English for example, I doubt there are non-contrived examples of sentences which have more than 2 levels of sub-clauses.

I think the interesting thing about recursion in language is precisely that we rarely see deeply nested examples yet we don't seem to have issues parsing deeply nested examples when they do occur (if they're not specifically constructed to be hard to parse). The fact that we probably didn't learn this by example might be an indication that our brains are somehow hardwired to look for regularity in grammar, including recursion.
4 of those 5 (all but Shell) are very declarative languages. They tend to be very concise and powerful, but are quite different from the more imperative languages people are used to.

Could be that once you really grasp them, you love them, but they’re harder to grasp because they’re so different?
This is very, very cool. It would also be amazing as a Photoshop filter.

But separately -- I've often wondered if the pixel grid is really the best way of storing compressed image data, and if something based on triangles couldn't be viable.

Just like progressive JPEG can render broad areas of color followed by filling in details, what if you used progressive layers of semitransparent colored triangle meshes to do the same? Or at least to form a base layer?

HEVC image encoding is already a big improvement over JPEG in that fixed square blocks are replaced by variable-sized blocks. But if we got rid of rectangular blocks and replaced them with flexible triangles?

It might be computationally prohibitive for encoding, and also you'd need to find a really clever way of representing triangles and colors in a minimal number of bits. But curious if anyone here knows whether something like that's ever been attempted.
Y Combinator didn't invest in either of these companies. With Theranos, most of the investors weren't VCs. The ones who were were had family/personal connections to Elizabeth Holmes. They've been made to look stupid, and everyone knows if they kept doing deals like that they'd go bust. UBeam had several top VC investors, but they must have been convinced that the original technology demo was legitimate, and that it could be productized and scaled. The skeptics against UBeam only came out later, after they'd already raised their big money. Again, they know if they keep doing deals like that, they'll go bust.
> if all existing diplomas were invalidated and the entire system of diploma-granting were to be stripped away from educational institutions, an equivalent would quickly be re-established by the free market - and it would probably resemble Proctorio.

coming soon to a tech interview near you.
Profiling virtualized GPU acceleration with Perfetto
Awesome!! I have it all outlined, just need to skim through the textbooks again and then type everything up. I’m putting up the philosophy list next week and then all my spare time will go into finishing the math one!