skysight-inc/HackerNews huggingface dataset:
I think you may have misunderstood the complaint, which is perfectly valid. A few paragraphs earlier:

> The downside to enums comes from how they fit into the TypeScript language. TypeScript is supposed to be JavaScript, but with static type features added. If we remove all of the types from TypeScript code, what's left should be valid JavaScript code. The formal word used in the TypeScript documentation is "type-level extension": most TypeScript features are type-level extensions to JavaScript, and they don't affect the code's runtime behavior.

And:

> Most TypeScript features work in this way, following the type-level extension rule. To get JavaScript code, the compiler simply removes the type annotations.

> Unfortunately, enums break this rule.

And then there is an explanation about why this is important: it makes life hard for tooling, especially fast tooling; for in the absence of such features, JavaScript tooling can support TypeScript with little bother, just dropping the TypeScript bits and getting equivalent JavaScript; but in the presence of such features, they have to either use tsc (slow!) or implement more TypeScript-specific stuff.

Compilation of most TypeScript features to JavaScript simply removes the TypeScript bits. Enums, however, have to be transformed, adding to the output JavaScript something that was not in the source JavaScript.
Analogue NFT Storage
I'm going to use an analogy from my hobby: because internal software is like shop furniture in a woodworking shop. Those things are mostly used in the production of other things that make the company revenue. It does its job, has room for many improvements, but isn't something you'd go out and sell as a product. It might be built from scraps, using crappy lumber and pieced together with whatever fasteners were around or cheap.

Open Source tooling on the other hand is like independent woodworker sharing plans with their community. They want it to be the best they can produce because they know their peers are going to see it, possibly use it, possibly mention it to others if its really good.
Ripping off business ideas is an aspect of competition (BK versus McDonalds), not sure it is related to morals…
In a pure quantitative basis, considering only the deaths and not even the social and economic cost (which indirectly leads to more deaths, or at least impacts quality of life) there's no much reason not to include tobacco into the list of great genocides.
Objectivelly, all those executives, salesman, advertisers are guilty of crimes against humanity.
The Java crowd indeed gave us god awful classes.

But before that there were countless competing models for creating objects or object factories.

Obviously, JavaScript is an object oriented language, too. You cannot escape that fact if you are determined to make the browser paint anything.

Classes effectively solved the "How?"

To pretend you don't need object orientation in JavaScript is really trying hard to make JavaScript into an entirely different language.
Cat 5e cabling (20 years old)@ 1 Gbps, 5 small switches of 5-16 ports, 1 Cisco router with 2 incoming internet lines, one on CATV and one on fiber (very cheap, less than $20/month each). Redundancy needed as the setup is used by 3 families with 2 people are working from home permanently and several kids doing school online from time to time (on Covid peaks).

2 servers, about 40 devices (including ~10 phones), 2 WiFi access points. Looking for 10 Gbps fiber in key places, but other than affordable Mikrotik switches I was not able to source the components. Several computers have 2.5 Gbps onboard, but good luck finding cost-effective 2.5Gbps switches with 10 Gbps uplink.

I have no recommendation for switches, availability and price is very good for 1 Gbps. For access points any decent Wifi 6 from a reputable manufacturer should be fine.
I think TypeScript loosely mapping to JS is important if just because JS sourcemaps suck, like they're so often randomly ignored in callstacks etc. And JS semantics are so subtle it makes transpiling any other language a pain.

But this doesn't justify removing every codegen feature. Namespaces and enums won't make your code less reasonable, and moreover they're just syntax sugar, they don't change actual JS semantics.
Microorganisms have been using antibiotics against each other since life begun on Earth and have evolved ways to evolve around them and develop resistance. For a drug to become ineffective, its target needs a possible evolutionary path around its effect. Depending on what the drug effect, it's possible such path does not exist.

Of course, as Jeff Goldblum wisely said, life always finds a way. We can only hope it takes a long time for that to happen.
> The downside of on-demand is the pricing - it's more expensive if you have continuous load.

True, although you don't have to make that choice permanently. You can switch from provisioned to on demand once every 24 hours.

And you can also set up application autoscaling in provisioned mode, which'll allow you to set parameters under which it'll scale your provisioned capacity up or down for you. This doesn't require any code and works pretty well if you can accept autoscaling adjustments being made in the timeframe of a minute or two.
Same here. I had bad neck and back pain, and it was relieved after a few minutes in the tank.

I love massages (which are probably better on the muscles due to increasing circulation), but I feel that tanks are better for the mind. Although floating would relieve strain on the back and neck!
I just realized that my original post didnt address what your wrote. Its retained below the line for posterity

First family corruption isn't something of “the last half decade”, implying Trump. Its goes back way further and American don’t like, want it gone and whenever evidence of it appears they want heads to roll.

Second, if we’re comparing to the last half decade, then it stands to reason that prosecutors should be sicced on the first family as the Trump family was. Fair is fair, afterall.

_____________

If you accept that the laptop is not a fake (a point that was conceded by traditional media after the election), the laptop contains substantial evidence [1] of corruption and sale of access. Furthermore it contains evidence that the president knew about it and was the coordinator behind the scenes (including Hunter complaining that his dad was taking too large a cut).

Now, before we get too excited, I think what’s on the laptop is par for the course in DC for either party. Its just the Joe has the fortune [2] of having a particularly inept son.

[1] I use the word “evidence” on purpose, as opposed to the word “proof”, that is to say it contains pieces of evidence that has to be validated, contextualized, etc.

For example, are the ppl that have come forward claiming that a certain nickname refers to Joe Biden lying?

The laptop is real, this much is widely conceded, but were the material published on right wing media really on it, or are they a fabrication? Or are they cut outs out of context?

But, prima facie, it doesn’t look good.

[2] I originally wrote “misfortune”, but no child is unfortunate. I really didnt know how to write this sentence in a way that

A. Conveyed my belief that Joe’s son causes problems

B. Joe’s son is a blessing for Joe and his family

EDIT: grammer
https://www.boredbutton.com/ is one pretty high-traffic example
> But they knew the material to the point that it was trivial for them

On the flipside this can make it harder for the teacher to relate to the students. In a university context of course, students have each other as equals.
The Amazonification of Royal Mail
Causing random connections on your motherboard to flex thus making/breaking any flaky ones, you might introduce errors into your state.

Real server hotswap hardware is not putting any force on the motherboard; it goes into a caged connector.
Streaming is really just another payday for the winners of the popular music boom of the 60s, and more particularly the IP holders. They got to have their cake with the original vinyl sales, eat it again in the CD era and now they can rent it out permanently via streaming. And they're not interested in sharing any of that out with emerging musicians.

In the past, there was enough of a barrier to just getting music onto disc and out on the airwaves that labels would have to invest in 100 acts just to have one breakthrough. So they'd need to take some of the winnings from their biggest selling artists and reinvest them in new acts to stay in the game. But now they can get income from streaming rather than sales - there's much less incentive to keep new records and artists coming through. If anything it makes more sense for them to just sit on their back catalogue and squash anything new.

So nobody's going to invest the comparatively large amounts needed to get unknown bands into good studios to record albums any more, let alone fund them through the difficult second and third albums often necessary to get traction. Emerging musicians can only do what they can at minimal cost - hence much more of a move towards electronic and bedroom production. That can have great output now due to tech advances in home recording, but it's not gonna be the same as putting musicians in fully kitted studio. (And things like a shift to high-loudness, low dynamic range are another side effect of the ways that music is distributed and consumed, plus advances in what's possible with digital recording and limiting).

The article kinda touches on this stuff but what it doesn't really seem to acknowledge is this is just what's good for the industry. Big labels are perfectly happy picking the winners that blow up on Youtube - it just saves all their development costs. The whole thing just works for them - their interests aren't in having a diverse range of music produced, allowing for a living for artists that aren't their big cash cows, preserving particular genres or recording styles etc.
The trick is to structure all of your emails in rhyming meter; it helps your descendants recognize and correct errors in transmission.
Stack Overflow is sunsetting jobs and developer story
I use a few secondhand Netgear R7800 with OpenWrt installed to blanket the house in fast WiFi and 1Gb Ethernet. This setup has been in place for almost 4 years now and has been very reliable. Maintenance is needed to keep software up to date.

With so many radios, I've segregated IoT devices on their own frequency to maximize throughput on workstations. VLANs provide network isolation.

I think the routing performance is fine for most households. If you need a router that does QoS on a gigabit internet connection, you'll need something more powerful.

Occasionally I'll wish that I had something faster than 1GbE, so the hunt for hardware continues...
What I like about TypeScript is that all these features are optional, declaring that they should be avoided is going too far, bus so would be saying that you should always use all features of a language if it could apply.

Everything has its place, and for allot of the features of TypeScript I think they are designed to be useful when you have a large number of developers working on incredibly large codebases.

I suppose in some ways it's like C++, you can decide to fully embrace all of its features, or code in a much more C like way, just taking advantage of classes.

It comes down to personal/team preference, what works for you.

Personally with TypeScript I'm inclined to code in a "closer to JavaScript" way (but taking full advantage of types obviously), but would happily work in whatever style was prevailing in the project.
You might like this story about Freeman Dyson and Richard Feynman having a road trip:

https://youtu.be/1Rr3ZWt1ULQ (the whole interview is very interesting and contains a lot of stories of meeting other physicists and mathematicians, it’s broken up into a series of snippets of a few minutes each on youtube)

In the end this trip lead to one of Dyson’s biggest contributions to physics, he could talk to Feynman about his research on the road trip and visited Schwinger afterwards and as such was in a unique position to recognise and formalise the equivalence of Feynman’s, Schwinger’s and Tomanaga's formulations of quantum electrodynamics. This was an important step towards the acceptance of Feynman diagrams.

I also really liked "Maker of Patterns”, Dyson’s autobiography through letters.
The only type of geoengineering I would endorse without much hesitation is sucking CO2 back out of the atmosphere. But I don't think that the weather system is sensitive enough that we can't try nudging it with measures that are easy to stop and whose effects only last a couple of years (e.g. injection sulphur into the atmosphere).
Ask HN: How to build a customized board from scratch with edge TPU?
If you maintain the same interface (same classes, methods, types, etc) it seems to me a module ought to be hot-reloadable within the same process. This is already possible with a loosely-coupled plugin architecture and I could see it being an integrated part of a language.
I’m going to stick my neck out and say that Facebook made the right call here.

The problem isn’t the content, but rather the audience, and how they react to said content.

People generally don’t read articles - particularly lengthy articles, particularly articles written by academia for academia - they read the headline, perhaps the lead, and then go post and spread their interpretation of the information.

The BMJ have a reputation as being a reputable source of information.

Take these two together, and you have a wavefront of posts claiming that the BMJ agrees that vaccines are dangerous and poorly tested, and the story isn’t what the article holds, it isn’t nuanced, it isn’t moderate, it’s “look, this proves that bill gates wants a microchip in you, and the BMJ confirms it!”.

So, you have a difficult choice. Do you allow a factual article and the reputation of the BMJ to be used as fodder for anti-vaxxer sentiment, or do you try to dampen the squib and decrease the propagation of the distorted interpretations?

If anything, there should perhaps be a middle road, where in order to share or comment on an article, you have to answer a series of questions about what the article says. This would dampen the network effect, and would hopefully ensure that people are actually forced to read the content they’re sharing, rather than relying on a headline and a strapline interpretation added by the sharer.
Mass produced bread can be produced like that. There's nothing about the concept of mass production that forbids products from taking a long time to produce.

Maybe in the US, nobody mass produces bread like that.
The government has known this as part of the covers program ever since the 2000s (or before). Informed delivery is just letting people do something useful with that information, which is a welcome change from other nasty surveillance programs.
Both my desktop and server have a wifi hop in the loop.

Short, line of sight and 5ghz though. Perfectly stable.

So it can be fine…under ideal conditions
Saying there's proof and there actually being proof are two very different things.

Show me the proof.
The commander of that camp was sentenced to 3+ years in prison after the war, and some of the inhuman behaviour mentioned in the wikipedia article was that internees were held for 75 days without a proper trial. Meanwhile, the US is actively holding POWs without a trial for nearly 20 years: https://www.nytimes.com/interactive/2021/us/guantanamo-bay-d... — and the idea of accountability for US law enforcement / detention officials is considered tantamount to treason.

As for "worse than a German POW camp", as claimed by some US sources in the wikipedia article... nope. Even disregarding the stark discrepancy between the treatment of western allied soldiers and Russian POWs in German camps (of the latter, more than half died in the camps, many murdered outright), treatment of Western POWs was not all that great. As disgraceful as the conditions at Wauwilermoos for escapees from other POW camps were, this is what could have faced them in a German camp: https://en.wikipedia.org/wiki/Stalag_Luft_III_murders
I disagree with this. We have a reasonably large Angular application that is only going to get much bigger (hard to define what that means ... big telephony app with tens of thousands of customers). I am the lead and architect.

We use enums and private keywords. With the private keywords, all I care about is that it is logically correct. We use private when things are truly private, i.e. they are only called from within the same class and don't need to be made visible to the view template or outside of the class. I honestly don't care what this transpiles down to, the point for us at least is not to make things "truly private" (good luck with that in JavaScript). It's simply to compiler-enforce rules. We also have ESLint to ensure that our private fields are all below the public ones to keep things nice and neat.

I also enforce that we actually make things as public although that isn't needed, and I enforce returning void.

So instead of:

someMethod() {}

I have us use:

public someMethod(): void {}

Just to state what you intend.

I realize "I don't care what this transpiles down to" might really irk some people, but I really don't. In our C# back-end I am much more strict about this stuff, but in JS at the moment given the standardization of the #private fields and the fact I consider them really ugly, I honestly don't care. Just give me a clean code base that enforces we can't reference private fields and methods from our templates.

For enums, I recently wrote a method that does exactly what this article says not to do, use it for GET, POST, and PUT.

What would be a cleaner way to write this? If it has to be refactored into something much "uglier" I don't think I'd prefer it.

this.downloadService.fileWithProgress(url, RequestType.post, ActionType.download, body)

This is a service I wrote that handles real-time progress (i.e. show an accurate progress bar when downloading files). I think this is clean and logical.
> as it was really hard to hire Scala developers

This is by far the biggest problem of Scala. After Typesafe rebranding and dropping the ball as a main Scala supporting body, it all went downhill from there. Ehich is a shame as Scala is a solid language with very good features.
I see the next to zero codegen in typescript as a strategy: it removes all discutions about languages features besides typing, guarantees next to zero issues in production in case of code generation bug, making compiler deliveries safe and avoid need of coordination in toolchain.
Not the person you're replying to, but I have had part of the hinge break in an HP laptop.
There are not so many birds flying in the night, drones also are not present everywhere. But a satellite which reflects the light of the sun really can ruin your hobby.
I came across an interesting tool for creating fillable forms recently released by OnlyOffice. I think it looks promising and thought it would be worth sharing, even though the article title is self-promoting, since it was written by OnlyOffice to market this feature.

One of the challenges I have is creating an editable fillable forms (in our case test reports) from a Word Document that I can keep updating and publishing to PDF. Libreoffice and Word and Form Tools, but I have not found that they translate well to PDF (if at all) or are easy to lay out. While I have not used Acrobat, I have also tried FoxIt PDF Reader and PDFOffice by Readdle before it was discontinued. The main challenge with those two is that the auto-detect form would not detect fields and place fields where they were not needed. Additionally, any time I needed to update the form, I need to autodetect the fields again, and following that, convert them to other types, like dates, signatures, and more. In this respect, FoxIt was even more limited because all autodetected fields are text boxes and cannot be changed to other types: Any non-text field has to be manually laid out.

The main benefits of the solution by OnlyOffice is that you can take a word document and save it in their OFORM file format that is an extended form of .docx . Following that, you can add fields, continue editing the document, and publish revisions to it to PDF. The limitations so far are the limited types of fields currently available. There is no Date Field or Signature Field, which is significant. I also don't see an option to clone a field so data entered in one field is autofilled in another field on another page. Hopefully will get addressed in later releases. Despite that, I think it is still going to be a time-saver for myself.

Note: I am not affiliated with OnlyOffice. I came across this on LWN and then across more information on the form functionality, which I thought would be worth sharing, and got approval from Dang to post this (https://lwn.net/Articles/881812/).
Despite the large amount of criticism in the comments here I think that the point the article makes here is pretty valid.

The described features are not what TypeScript itself wants to be, and I think if it wasn't for backwards compatibility the team would remove some of them.

IIRC namespaces as well as the `import = ` syntax come from a time where ESM wasn't a thing yet but a module system was very much needed. So now that ESM can be used pretty much everywhere namespaces can be avoided and therefore reduce the learning surface of TypeScript.

Enums IMO have no advantage over union types with string literals, e.g. `type Status = 'fulfilled' | 'pending' | 'failed'`. They map way better to JSON and are generally easier to understand, while still benefiting from type safety and typo protection.

Well the private keyword is kind of like namespaces in that it came from a time where the feature was needed/wanted, but the EcmaScript spec was not moving fast enough. So they made their own version of it which is now obsolete.

And for decorators, IIRC the decorator spec has already moved on and TypeScript's implementation is no longer up to date with it. And the spec itself is only stage 2 as mentioned in the article, so I wouldn't recommend using decorators either, you will face breaking changes with them some time in the future.

Furthermore, it is far more likely that you run into trouble when using one of these features with a compiler that is not TSC, e.g. esbuild or Babel. Decorators have never been working all that well with the Babel plugin. Enums are probably fine here.
Does it allow having a catch-all email address?
Software polishing is usually tied to the number of users/customers. In my work, I use industrial software. It is expensive, and unpolished. Users are expected to train on it, learning it's unique quirks as a skill. The more software requires skill/knowing it, usually the less polished it is. Obviously, not programs such as Photoshop, but merely to run a machine, definitely.
It’s great that you already have an idea of how this was done; others may not. There’s a lot to talk about there for people unfamiliar, don’t you think? Saying otherwise would be very close-minded.

It seems to me from your other comments in this thread that you’re intent on being negative / reductionist to others work without offering much to the conversation, so I will happily disengage with you now.
Thanks.

The original site has an obnoxious cookie popup that covers the whole screen and more to the point here you have to scroll to click the buttons on mobile.