skysight-inc/HackerNews huggingface dataset:
I was talking recently to an Indian colleague whose son was admitted to McGill as an CS undergraduate. He had a very smooth transition through Canadian customs. Then was met right on the other side by representatives from McGill who provided a phone (to call his mother in India), a meal, and then talked him through the process of working with Canadian immigration to apply for permanent residency in a few years if he wanted to stay. The contrast with the US approach could not be starker.
There was a plugin to do this on Vbulletin forums.

It was somethink like a shadow-ban but where you would give random timeouts/slow loads to the user
The problem is not so much the absence of generics but the availability of crazy reflection at runtime compared to the rigid type system at compile time. There absolutely is a lack of balance here.

All these things were already pointed out 10 years ago and were met by "you don't need that with Go", "Go back writing Java" sort of contempt, which gave the Go community a bad reputation.

Go could have been fixed 10 years ago if Rob Pike and co listened. They didn't want to because they thought they knew better than everybody else. ADA already fixed the genericity problem while keeping things readable with a limited form of generics as incomplete types.
The Common Lisp Condition System – Upcoming Book
then you haven't been paying very much attention have you
My wife got me these as a wedding gift present. Didn't make a difference for me--maybe a little more contrast in the different "greens". The next morning my cousin and brother (also both colorblind) tried them on and thought they were amazing. My cousin had the viral marketing reaction.
https://idioms.thefreedictionary.com/riot+of+colours

Still doesn't make any sense ...
Great read. When requesting to join an org, how do you know which org admins to send the request to?
Can an extreme low carb diet be used as medicine?
Elegant doesn't always go with optimized aerodynamics.
Thanks for mentioning. Wasn’t aware of it, see it on https://alternativeto.net/software/passbolt/?platform=self-h.... Wish you all the best.

Having a migration tool, would make considering a migration much easier ;-). No immediate plans to migrate BTW.
Author here. The book has just gone to production and will be available at the end of the year in dead-tree and electronic formats.

The book happened because I got annoyed at the fact that there is no good reference that shows how the condition system works, what are the foundations required for it to work, what are the basic building blocks that it is composed of, and what are its uses, both in the domain of handling exceptional situations and, more importantly and less obviously, outside that domain.

The book also contains a description of a full implementation of a condition system that can (and hopefully will!) be used outside Common Lisp. There's hope that some languages will pick up these parts of Common Lisp that fully decouple the acts and means of signaling conditions from the acts and means of handling them, therefore allowing for means of dynamically controlled control flow that are currently very hard to achieve in other languages.

The accompanying code is available at https://github.com/phoe/tclcs-code and https://github.com/phoe/portable-condition-system - it will be copied over to the Apress repository soon.

Linked Reddit thread: https://www.reddit.com/r/lisp/comments/hrjzs8/

AMA, I guess.
Somehow I hadn't made the connection that WhatsApp sounds like "What's up" until now.
The main benefit I see here of Python over C is when your program doesn't work (yet): Python has nicer error handling built straight into the language.

If you just want to present a working implementation, both C and Python can express readable versions.
Joe Armstrong spoke of "the mess we're in" and I think he captured it well. He was referring to the symptom in general, where-as this essay is about one of the root causes.

Having recently learned bits & pieces of Kubernetes, I can see the author's perspective as it's one I held for some time. Kubernetes is useful and makes many things easier. In exchange you give up finer-grained control and you have to work with an abstraction. Such is the nature of all abstractions.
I imagine that the Bay area is more than usually filled with aggressively ambitious people, projecting "fake it till you make it" success to both themselves and others. If everyone around you does the same, anything less than "perfect" makes you a loser, which conflicts with the self image you are cultivating. Therefore, everything must be as amazing as possible just to keep up with the rest. A sort of real life instagram syndrome if you will.

NZ (and other parts of the world as well, like the Nordic countries) have a similar reinforcing loop but in reverse. Excess boasting is seen as offensive, so nobody does it, so the average behavior trends towards modesty, making boasting stand out even more.
My most challenging bug was fixing a memory overwrite of a COM reference counter (of all things!) that would only happen under very rare conditions - when a 3rd party C library that was compiled with different calling convention would be called with a certain amount of parameters. It took me a month to chase down - frankly, it would have been impossible for me to figure out if Visual Studio did not have data breakpoints implemented for C++. It took a month... and the fix was also a two-liner. Still proud of that fix 17 years later!
WhatsApp sounds like "what's up" - it definitely suggests conversation

The other two are meaningless, but at least monosyllabic - "I'll Skype you," "I'll Slack you," "I'll ... Element you?"
I probably can't tell this story correctly because it is 2nd hand but ...

I was on a browser team. A fellow co-worker decided to add the Fullscreen API to it which means not just add the API but first discuss it in the relevant standards committees.

I'm pretty sure he thought, and so did management, this would be a 2-3 month project at most. IIRC though it was like 18 months, maybe longer.

Some problems that aren't obvious at first

* What is fullscreen mode? Is it a mode for the page, a mode for an individual element? What?

They eventually decided it was for an individual element

* What happens to the CSS above that element when none of its parents are being rendered?

I'm sure that took a while to argue over. Like if it was position: relative or absolute and suddenly it's parent is no longer displayed. What if the parent has CSS transforms? Okay, you say we ignore those and consider it the root element. Okay so does that mean none of the other styles from the parents apply like color or font-family? If some do and some don't we now have to go through every CSS property and decide if it does or does not continue to inherit. I don't actually know the answer to this.

* You have a DOM A->B->C->D->E. C asked to go fullscreen. While there E asks to go fullscreen. User presses ESC or whatever to exit fullscreen. Should it pop back to C or A? Does it matter if E is a video element and they clicked fullscreen? What if C is an iframe does it matter?

* Testing across all devices that support it requires all new testing infrastructure because going fullscreen is effectively something that happens outside the page not inside so testing that it actually happened, that a user can actually exit it correctly, requires entirely new test systems that were not there for previous APIs. Then multiply by 5 at least (Windows, MacOS, Linux, Android, ChromeOS, ...)

And so even though I'm sure everyone ended up understanding that, it turned out to be way more work than anyone expected. Yet, in the back of their minds it was arguably always "this is taking way longer than it should, goals not met" or at least that's how it seemed to be perceived.
or kik or discord
sort of, but it is the gap that is the issue. Today, tesla seems so far away from that goal that this amounts to false advertising. it's so far that one can actually doubt that they will achieve it in our lifetime.

whether or not you think tesla is close, just drive a tesla on a narrow road in Germany.
It's the endless pursuit to personify business. It comes from middle management being mostly uncreative and lifeless drones.
How is having generics/templates to reinvent the wheel?

The one thing that put me off the most about using C for everything is lack of a common list/vector/map/set standard library for all types. Instead I reinvent the wheel in each project. Go cheats in this regard with compiler magic and that just pisses me off. Atleast you can in theory do printf in iso C.
Not being able to look at the keyboard is actually a good way to learn.

Of course you'll have to fight your muscle memory and type at 20 wpm for a couple weeks. There's no shortcut.
I worked from home for years on a 2mps symmetric link from a wireless ISP in Tanzania, video conferencing worked well enough (Google Hangouts or whatever it was called 5 years ago).

For the heavy uploads I usually resorted to doing the upload from a VPS instead though, when possible (build the artifacts from that VPS, so that both the build and upload are much faster).
> Why would I pay at least 450 euro per month for something I have to run myself?

Some people/teams/departments are busy with other things, so that amount is worth the cost of outsourcing a service such that the team members can focus on other things.

Also:

* why would anyone run RHEL when they can run CentOS? (The cost of a service being down is more than the support fee.)

* why would I go to a restaurant when I can cook a meal at home for much less?

* why would I pay for a car wash when a garden house and a sponge worth just as well?

Also also, you may want to actually check what the pricing is:

* https://www.passbolt.com/pricing/pro
Coding Adventure: Procedural Moons and Planets
> I get it that when you say “how are you” in America, people are usually not asking how you are actually doing.

That’s not quite right, it usually is really asking that question, however, the space of acceptable responses (both in range of acceptable tones and maximum level of detail) varies widely based on context and relationship with the questioner. You are usually safe treating it as if it were an empty ritual to which the correct response is “fine, and you?” (unless it is already being echoed back to you), but that's not quite what it is in most situations.
There is an existing discussion to add threading to Element: https://github.com/vector-im/riot-web/issues/2349. To sum up, the backend already somewhat supports it by tagging a message with a `thread_id`. Then the UI can group messages by their `thread_id`s.
Shadowbanning in its different forms would be the best option, don't let the user know they have been noticed.

Let them think they sent messages and comments to other users, but don't actually deliver them.
Xiaomi Ecosystem Product Launch – 20:00 GMT+8
What an incredible amount of privilege you got there
slack is not very original if you think about it.
Because the three liner is easier to read
>The federated nature and ability to self host are really important to them.

It's important to everyone, whether they realize it or not.
> if you raise your children well

straight up no true Scotsman. Literally, no true Scotsman.
It's not about seeing "correctly". No human can see colour perfectly. It's about making it easier to distinguish colours that most people can easily distinguish. If someone came up with a way for me to distinguish more colours, e.g. like a tetrachromat can [1], I'd be keen to try it.

My father is red-green colourblind, so I've seen some consequences of it. I consider it a disability (there are ordinary things my dad just can't do), but it doesn't require fixing.

To most people red and green are as different as black and white; imagine having trouble distinguishing black and white, and you'll have an idea why some people think you might want these glasses. (Yes, I'm making assumptions about your vision here that might not be correct.)

[1] https://en.wikipedia.org/wiki/Tetrachromacy#Humans
We need to pick our fights carefully...
I'm not sure I got across what I mean.

Ones target should be shipping features. If you use 10k LOC to get a feature out, or 500 lines of more concise, optimised code, what matters is the feature.

If you have LOC targets to meet you are incentivised to produce the former rather than the latter.

My point is that a high number of lines isn't as important as good features. Though the two can get conflated
>Why do peasants in Africa have more children than Lawyers in New York

Because below a certain agricultural productivity level having more kids is actually beneficial for your economic success. Once you get over a certain productivity level it makes sense to have fewer kids and invest in them moving up the economic ladder.

>Builders in Arkensas have more kids than tech workers in San Francisco?

Because the cost of every warm body in a household in SF is completely asinine so people have fewer kids than they would like to.
Yes, https://en.wikipedia.org/wiki/Treble_damages
Well, in most countries, you get external funding from childless people which are paying higher taxes... If people were to pay entirely for the education and health of their offsprings, they would be way less babies in the developed world. And I don't even mention externalities. A human being in a developed country has a big impact on the environment, if people had to pay for it, having a child would out of reach of most.
It's not so much about the algorithm, but the parsing itself.

Parser combinators give you one of the most straightforward ways to express parsers.

You are right, that the language you express your parser combinators in vs the language you express an alternative solution in also will have an impact.

You can in theory express parser combinators in Python. But it's gonna be a bit ugly, because Python has relatively clunky syntax for functions.

Some people have tried writer parser combinator libraries for eg JavaScript. See https://github.com/GregRos/parjs

I just found a parser combinator library for Python https://pypi.org/project/parsita/ But it looks like they have to abuse some Python magic to make the code readable.
> I'm not wholly convinced the first statement is the case.

Probably because you're only thinking about it from a US-centric POV.

As a Canadian who lives under a Westminster-style style system, there tends to be less gridlock here under majority governments.
I've worked for or had Element as a client a couple different times in my career. Each time, it was a different company. The name is rather elementary.
> A shrinking, aging population would fix this problem. The demand for labor will go up, the supply will go down. Bad for the investor class looking for profits, good for reducing economic inequality. People will be able to profit from labor again.

Except in terms of pure economics, labor won’t necessarily become more valuable, because with less population there will be less consumption and less demand for goods. So even though the dwindling supply of labor will have an upward effect on labor’s value, the dwindling demand for goods will have a counteracting downward effect. And this will only be exacerbated by increased automation.

Economic inequality and lack of economic opportunity is going to be a problem regardless of the population growth rate, and the solution will require something more substantial than simply have less/more children.
My problem is that I need to be able to check where the keys are to be able to learn it in the first place. I can touch type quite well, just not type at all in a layout I never used before, without being able to look at the keys.
Since when does a monopoly mean "a very big market player"?
I live in Ireland. This is a sad day. For years now I've been wondering what the Irish govt would do with BILLIONS of dollars.

We could have had an Irish space program! A monorail! We could have bought Greenland!
No, it's just that I'm not a native English speaker, I'm realizing just now that I checked on WordReference that "slack" is an existing word!
Samsung: Expect 6G in 2028, enabling mobile holograms and digital twins
> The average level of American "OMG so excited to meet you" is usually reserved for actual celebrities in Europe

I've been an American all my life, and I've never seen anyone say they were excited to meet someone other than either an actual celebrity or someone who has been significantly talked up in advance to the level of being at a quasi-celebrity level in context (and even in the latter case, “I'm glad to finally meet you”, possibly followed by an explanation of the reason they've been looking forward to it, is much more common than expressions of excitement.)

Honestly, the behavior you seem to be describing is one which would strike most Americans as both unusual and deeply disingenuous.
Dozens of users will be effected by this
The infamous goal post moving.

rglullis, I'm also interested to pay you tons of money. sadly I will only pay for service powered by unicorn's farts and looks like your isn't. When do you think you can arrange that, I literally have my magical credit card in my hand?
Spain is similar. 30k max for junior dev. Getting above 50-60k means you're either a hero, or Batman own son.
You still have to understand how things are implemented by others (even at a high level view: ex: what is a RDBMS index) to be aware of their advantages and drawbacks to make the best use of algorithms available to achieve your goals (ex: performance of the solution, ease of evolution of the solution).
Zulip needs a couple UI/UX designer to work on it and get a facelift into the "cutesy and smiley interfaces" era. It's great, and it's the only one that's actually free to self host with all features.
User ‘about’ checks out
I created an Emacs minor mode to make the ö/ä keys type square/curly brackets, but it’s not ideal.
How young were you when you got married and when you started having kids?
I have been using this for last 6 months. Apart from all these issues, search for a chat in a conversation is not possible.
> A shrinking, aging population would fix this problem. The demand for labor will go up, the supply will go down. Bad for the investor class looking for profits, good for reducing economic inequality. People will be able to profit from labor again.

There is historical evidence of this, like consequences of the Black Death:

"Another notable consequence of the Black Death was the raising of the real wage of England (due to the shortage of labour as a result of the reduction in population), a trait shared across Western Europe, which in general led to a real wage in 1450 that was unmatched in most countries until the 19th or 20th century. The higher wages for workers combined with sinking prices on grain products led to a problematic economic situation for the gentry."

https://en.wikipedia.org/wiki/Black_Death_in_England
This proposal seems very non-composable, by which I mean that the syntax does not integrate with a number of other features. He says that currently you can’t nest it in other expressions for example, and you can’t use it with arguments starting with a parenthesis.

I personally like the aesthetic of it, but the non-composability makes it a UX mess in my opinion. Languages are a toolset for combining things, and when those tools just arbitrarily refuse to be combined (or combine irregularly), you end up bending over backwards to make the language get out of your way rather than getting a job done.
> "this should be easy to do, right?

Yeah, couple of months - me, every time.
I love this, although I can't help but think this is such a capitalist solution to this problem: private detectives, private whistleblowing, private bounty hunters. The american market is obviously better without those frauds, but what does that mean in the long run ? Any fraud under this threshold (without whistleblowing bounties, or too small bounties) can continue happening ?
Microsoft urges patching severe-impact, wormable server vulnerability
Hell, if you can find a construction worker that somehow, magically can build the wall with 200 bricks instead of 2000, everyone would want to hire them because they’re saving them 90% of the cost.
Discord=argument=discussion
The only mistake of the procedure is that if you don't have enough info you should ask for help before. This is very common and I have done that so many times to understand it's a waste of time. The only exception IMO is when you really need to understand certain parts of the codebase at a very low level so spending time solving things by yourself it's well worth as an exercise and helps a lot. If it's a part of the codebase you're not likely to be working on any time soon, just don't do it. Talk to whom reported the bug and also talk to the last person that worked on that piece of code (git blame is your friend here)
Yeah, me too, the whole appeal of Go for me was that it was as barebones as C (with GC and concurrency). It was a breath of fresh air. Generics opens the door to the abstraction olympics in other "modern" languages. Might as well just go back to Java.
Poor people in San Francisco have more kids than rich people in San Francisco. The explanation just doesn't fit the data.
Btw, which three-liner do you mean?
This was the focus of my advanced algorithms course at Georgia Tech in my senior year. We had basically a full semester on random algorithms, and I remember walking out each day feeling like the fancy algorithms I'd memorized the previous year were a bit less glamorous.

The number of algorithms that removed multiple complicated stateful steps with 'and we randomly select an element from the array' was mindblowing. As I work on more and more distributed systems I keep seeing opportunities for simplifications with randomness (with obvious drawbacks on occasion).
Banksy Hoodies and T-Shirt 25%Off Sale
If you are Looking For a Lightweight Hoodie, T-Shirt, Classic T-Shirt, 100% Cotton T-Shirt,
Lightweight Sweatshirt, Free Worldwide Shipping

sales@banksyhoodies.com
https://banksyhoodies.com/
I know, it sounds bliss! Like the 1980s - fewer distractions, clearer thoughts.
Using a chat software for keeping history is the wrong use case. I've had to add some minor chat functionality to one of my side projects and honestly the only benefit of a chat history is that when you join a server/channel you get to see the last 20 min of the conversation instead of an empty screen. I automatically delete chat messages older than one hour. Different use cases might need completely different limits but it doesn't change the fact that you should pick a cut off point beyond which you start deleting messages.
Persistent data structures don't have to be immutable. (The Wikipedia article explains.)

But immutable data structures are always trivially persistent.
see https://youtu.be/m05abdGSOxY
Learning Rust by Comparing it to TypeScript
Hungary's Leading Outlet Became the Target of Political Control
GNU Toolchain Continues Phasing Out Native Client Support (NaCl)
Both myself and another remote coworker, this is our situation, although it is closer to $60.

6Mbps/768kbps DSL
I liked the alternative proposed later in the thread:

gen T type pair struct { a, b T } // contrast with type pair(type T) ...
gen T,U type W struct { a T; b U } // contrast with type W(type T, U) ...
gen T func Print(s []T) {...} // print a slice of T

or using `forall`

forall T, type pair struct { a, b T }

V readable IMO
Participant-Led Research in the Quantified Self Community
Except there is this little thing called documentation and user manuals that one has to write on our native languages, yes even code comments.
You can notify without email though. If the patform itself is communication related they can send you in-app message.
The children who exist after you made them.
I mean I deliberately said the equivalent of "True Scots usually wear kilts, but some don't," so not really.
The problem is that this leads to a raised prices due to foreigners' purchase power, and this pushes locals away. This is very problematic politically as very few people end up profiting from tourists.