skysight-inc/HackerNews huggingface dataset:
I think while this is true, one thing that was lost with PHP style development is a model that's an easy stepping stone from "a directory full of HTML files".

With PHP (and other things like classic ASP) the model was the exact same - it's just that instead of an HTML file, you would request a PHP file and then that would be what was run. The output of that file is what the user would see.

With modern-day backend frameworks, that relationship is severed. Your user makes a request, it goes through a bunch of "stuff", and ends up executing a function. How that happens isn't nearly as obvious. It's learnable for sure, but it takes what is a 5 second explanation to something that most brand new developers chalk up to magic for a while.
I guess inscrutable error messages are a "feature" of ML-like languages. I have not used OCaml yet, but the first few years with Haskell probably have been just as rough in terms of parsing type errors.

Haskell has a few niceties when trying to debug type errors nowadays. For example typed holes that allows one to spice in `_` within code and the compiler will tell you what type it expects you to replace that hole with, alleviating many issues I had previously. But in the same sense I'm in agreement with you, and I've been more productive when writing Guile/Chicken Scheme code for small tools.

Interestingly I've binged on OCaml videos recently, because I would find it interesting to work with it some day. From a distance what I like about it (aside from the functional language goodness) is that it supports objects, has row polymorphism, optional arguments, and imperative constructs (I sure like my mutation heavy for/while loops when prototyping code).
SEC to Hire More Crypto Cops to Fight Digital Frauds
I think what is not mentioned nearly enough is the need for isolation to prevent decoherence of the cat. You need to make sure the box is it's own universe totally disconnected from the rest. Then I'd say it is a little more intuitive that parallel insides of the box might exist in superposition.
That's silly for electricity.

Electricity will never, ever be a free market. The barriers to entry are almost insurmountable, especially capital requirements (production + distribution, especially distribution) but also the myriad safety regulations.

Might as well involve the government and gain some accountability, because with corporations, there is 0 accountability.
Because smart pointers are still pointers under the hood. You're forgetting the time before you know what pointers were - people coming from higher level languages don't immediately grok the concept. By teaching them automatic memory management patterns like we use in C++ without teaching them why you need such things, they'll never fully understand the code they're writing.

It's like the "I know React but not JavaScript" crowd all over again.
I wouldn't have though that the power lines would be the biggest issue for nuclear power in regard to NIMBYs. And even then any generation method would require installing power lines...
I’m pretty confused about how bad this post is considering how smart Gelman is? He’s making facile arguments even if you ignore that he hasn’t understood what either steelmaning or strawmaning are. I would say more, but other people have covered the errors in other comments, and I just wanted to explicitly note my confusion about how Dr. Gelman could have written this.
Dark Patterns in Personal Data Collection: Definition, Taxonomy and Lawfulness
Maybe you mastered it better than me but I always found Cinelerra-CV a bit clunky, especially if I was dealing with oddball formats (HDV) that I didn't understand. Maybe I would get the hang of it now but I've kinda moved on.
Mastodon explicitly doesn't follow these kinds of opaque algos for recommending tweets.

The risk that someone will create a "knock-off" twitter? Give me a break. Anyone could do that at any time, there's nothing special about Twitter except the enormous network effect.

The only risk I can see in open-sourcing the code is that it would make it easier for people to game the system and attack it in the short run. But opening it to scrutiny and review will make it more robust and less susceptible to attack in the medium-to-long term.
So is this based on Servo or old-school Gecko?

From skimming the repo, looks like the latter. Too bad, I was hoping Igalia had figured out a way to finance Servo development.
> Emacs is really starting to show its age.

I disagree. I came to Emacs from a combination of VSCode/Pycharms and Jupyter notebook. I think the latter are still held in highest regard in the IDE space. To this day there is nothing in another editor or IDE that I miss. I find that Emacs allows me to invest as much as I want into my tools: editor, notebook, document generator, and shell. If you are looking for a maximal out-of-the-box product, then sure Emacs will come up short. However if you are looking for a product that you can develop and use for a lifetime then personally I don't think any one piece of software comes close

NOTE: Emacs ecosystem has had support for multiple cursors for over a decade. Emacs (like Python) should not be valued in terms of built-in features, but in terms of its community and ecosystem
>cannot emulate a dumb calculator accurately

Neither can people, for the most part.
The term “server-side rendering” was in common usage when people started implementing client-side rendering more commonly in the late ’00s and early ’10s. But in the last five years or so, the term has been appropriated by the isomorphic rendering crowd so that “SSR” or “Server-Side Rendering” normally means server-side isomorphic rendering (that is: server-side operation of something that’s primarily designed for client-side rendering), and there’s no standard term any more for pure server-side rendering, though if you write it lowercase it probably means the old-school technique.
If this is the app:
https://apps.apple.com/ch/app/school-morning-routine/id16068...

The I notice quite few things:
- low fps animations
- delay until the keyboard popups
- no support to save the password or use e.g. an Apple account to login
- no scrollbars in the modal and the back button out of view

So in general, this would not make the cut for the native apps my employer produces. Especially the low fps is a deal breaker.

Tested on an iPhone XR
They cannot be even half as efficient - the process of electrolysis is only 40% efficient, then hydrogen must be compressed to insane pressure (which can require up to 20% of the enrgy contained withing) and transporting across the country. Only like 25% of energy you started with ever arrives to the fuel station
That's what is promised under the term "no code" or "low code", but it's not how it actually works.

Low code and no code already exist and they are already successful where they work. For instance, you can now create a website using wordpress with quite a bit of functionality without coding at all. That _is_ "no code". And you can use Excel to create quite complicated logic and calculations with very little coding. And that _is_ "low code". Even using an IDE and a high-level programming language is in some sense "low code".

Pretty much every other usage of this term by startups or others is purely marketing and promising something it can't do. I wish it were different because then I could build things even faster with less effort, but from what I can see and what the last decade shows, progress towards this goal is made in different ways.

> Let’s be honest; in most situations, cloning an existing successful business is a pretty easy, well defined task. That’s why you get things like “here’s my free clone of strava” or whatever.

> Once the problem is solved, building it is easy.

Yeah, but the mistake is to assume that solving the problem doesn't require technical folks. Even if something is not technically difficult, it still requires a lot of work and skills to translate vague thoughts in human language into computer-executable logic that behaves as one wants. This will be solved once we have some intelligent machine that can do that. Once we have that, the world will turn upside down.
> You don't find a lot of new backend projects that go the C++ route.

TBF, C++ was never a great backend language. Rust "the language" isn't either, but "Rust the package ecosystem" might be one day (because unlike C++, Rust is coming out of the "web hemisphere").
The bottom line is that in our short span of time on this world all of our lives take on some sort of shape that in the end is comparable to one another.
Many of the choices people make, they make because of this biological limit imposed on us - time.

The result is winners and losers - good and bad lives lived and many fates left by the road starting from the time people are born. Outcomes influenced by where you grew up, by rich or poor, good or bad schools and so on.
All one can do if one find oneself at the bottom of the pile so to say is to trade ones time to offset bad beginnings.
But life is short.

Time is the greatest equalizer of all, and if i could i would choose to live forever.
They use flatpak (at least I think they do) for firefox. I just use the .deb for chrome.
> Minutes after I posted this article, the attack resumed. Same shit, different AS.

Noob question: was that caused by the article getting posted to HN? Or was it really an attack?
This decision will further weaken the credibility of the Court since Barrett, Gorsuch & Beer Boy paid lots of lip service to 'super-precedence' and how Roe was the 'law of the land' during their confirmation hearings. Unlike pro-choice Sen. Collins who was fooled, the liberal senators were not.

What's next for Republicans will be to ban abortion outright at the national level, and not leave it up to the states. Then the sanctity squad will come for your Plan B pill, contraceptives, gay marriage, etc.
Subjective perhaps, but I don’t think the soft soap stands up to scrutiny. Case in point, witness the absolute fiasco of this month’s “property lottery”. A shitshow of bad design, disastrous implementation, and consequently failed rollout, which somehow won’t be resolved for weeks. As for the market; anyone who tries to run a shop is in for a world of pain, forced to micromanage their listings using the clunkiest of tools, in an unstable market with limited price signals and irrational competitors. Fun? No sir. It’s a pain in the ass.

I can’t speak to GW2, but cherry-picking something you clearly think is worse sets a very low bar. I don’t accept that meeting a low standard is a reasonable expectation. A long long time ago I used to help run an Eve:Online corporation, and there the sophisticated economy and market systems made for a vastly richer player experience.

The point being, Square Enix can’t be taken seriously when they talk about in-game economic structures. Their track record is one of incompetence and indifference.
Honestly I see "steelmanning" as an emergent property of a completely broken discourse in the first place. The whole concept derives from the idea that we need specific terminology for when we're going to actually discuss things in a reasonable manner. It's basically a response to a group of public intellectuals who have emerged on the internet that spend more time building their brand and dunking on their opponents within their own echo chamber than actually trying to persuade people. And these public intellectuals are so well-read that they reinvented devils-advocate in their own bubble. It also stems from a kind of silly idea that the things we disagree over boil down to finding logical errors in each others positions, rather than emerging from deep-rooted differences in values.

In the example in the article there is just a fundamental difference in how those people see the world. One person thinks that by and large people are free to openly disagree with the consensus and would do so if they wanted to, and the other person thinks that disagreeing with the public consensus on controversial topics has such a high price that people choose not to do it. Depending on your experience in the world either of those two views can be right. In fact, you can pull examples on both sides of this - where contrarians have successfully changed the consensus and are celebrated for it, or have spoken out and been stigmatized for it. These opposing positions stem from such a deep difference in world views it's useless to talk about Ivemectin. So the issue here isn't steelmanning, it's that you're not actually discussing the point of contention.
When I made another Monkey Island
I do nostalgically miss the one PalmOS and one Windows Mobile 6 device I had of each. That might be mostly nostalgia though. Not sure. My love for webOS OTOH is still being sad it didn’t become a distant 3rd mobile OS. I’d likely be rocking a webOS phone. Possibly tablet right now. Instead of going from Windows Mobile 6 -> iPhone -> webOS -> Windows Phone 7 -> Samsung Galaxy Note -> iPhones since then. I used to mess up or break my phones frequently so some of the switches were because of that.

—-
Related. I have a lot of nostalgia and actual usefulness from jailbreaking iPhones too. That seems like it may barely be a thing now with iOS 15 changes.

Even an M1 Mac won’t run iOS/iPadOS apps if any of the SIP securities are disabled.
Strawmanning is bad because it's fallacious reasoning, so it cannot serve as valid evidence for a proposition. It's a waste of time if what you're interested in is figuring out what the truth is; it only serves to pull the wool over an audience's eyes, or (perhaps more commonly) feed your ego by giving you a stupid and evil imaginary enemy to fight with, like children playing GI Joe or Batman.

"Steelmanning" doesn't involve strawmanning any position, unless the position you're "steelmanning" is inherently dependent on a fallacy—specifically, a fallacious strawman version of some other position. If you can find a non-fallacious argument for a proposition, you have to use it instead if you're "steelmanning."

So I don't agree that "steelmanning" involves strawmanning some other position Y, except in the most extreme cases, in which the position you're "steelmanning" can be trivially dismissed. Most positions that people actually hold have some valid argument in their favor, and therefore are not necessarily dependent on strawmanning other positions.
I think one of Emacs' design decisions was deliberately not going fully functional, but having global state and different scoping (Was it "dynamically scoped"? I always forget, which one is which.), because threading everything through all the functions would be quite complicated.

However, it may be possible to interact with Emacs using Elisp in a quite functional way.
What I mean is this:

https://i.imgur.com/7huPvde.jpg

What does the insanely large truck have that enables you to off road and explore your hobbies, that the smaller one does not?
I did different setups over time, but currently settled on forwardemail.net for incoming catch-all custom domain and iCloud+ SMTP servers for sending.
It is a gamble. The question typically boils down to whether you are willing to gamble. I mean.. it is genuinely harder to make 'real' friends as you grow older. As a kid, there is no question of ulterior motives, because they are in the open. He has a console and a new game I want to play. We are best friends now.

As adults, it is turtles all the way down..
Well, Cook made sure designers never hold sway and cause damage again the way Ive did, the top design position at Apple (which is not at the C-suite or SVP level when relatively minor specialties like Machine Learning are represented) has been split between two people, Alan Dye and Evans Hankey, and they report to COO Jeff Williams, a mechanical engineer by training:

https://appleinsider.com/articles/19/06/28/who-are-alan-dye-...
I certainly found the article much easier to read when I turned it to black-on-white with no exuberant bolding and colouring of italics and the likes.
> I annotated the hell out of my programs, and completely avoided OCaml's type inference as much as I could because I saw that it could not guess what I meant.

The type checker and the type inference parts of the compiler are one and the same. If the type checker can’t infer what you mean you are most likely writing invalid code.

> Error messages like "This expression is of type X but an expression was expected of type X" were not uncommon, and super frustrating.

Ocaml is a strongly typed static language. As such your code has to respect type constraints. It’s very much a feature not a bug.

Still to be less defensive I too sometimes wish the error messages were more clear in highlighting why a certain type was expected but at least Ocaml provides tooling to live check the inferred type of any sub-expression while you edit your code.
When I hosted my own mail I did all of that except (e). I had trouble, as seems to be typical, with deliverability to Microsoft-hosted addresses. I wonder if (e) would have helped (doubt it).
Similar project that is also pretty nice and made it to the top HN fairly recently: https://mataroa.blog/
Eh, anyone know what has happened to Musk's starlink uplink boxes in the occupied zones?
There's also XAMPP
The Constitution was explicitly not a “here are your rights, and only these ones” document. The Ninth Amendment states:

> The enumeration in the Constitution, of certain rights, shall not be construed to deny or disparage others retained by the people.
We all knew Roe V. Wade was done as soon as Trump stacked the Court.
I'd trust it the same way as other open source projects.
what's wrong with the multiple-cursors package? I have been using it successfully for many years.

I suspect that emacs will outlast any replacements like it has done for the last few decades.
Cloud market dominated by AWS, Google, Microsoft (unsurprisingly)
Location: India

Remote: Yes

Willing to relocate: not currently
Technologies: Java, Python, Metasploit, Penetration Testing , Mobile app testing, Network Security, Wireshark, Nessus, Burpsuite

Resume:https://www.linkedin.com/in/ambika-prasad-swain-a63117152/

Email: ambikaprasad.s@vitap.ac.in

I am fresher recently graduated in 2021 looking for opportunities in the field of Cyber Security or related areas . I have worked part-time in Mobile application penetration testing and VAPT along with various projects in Web app Testing tools and Intrusion Detection . Keen and excited to learn and adapt upcoming future challenges .Interested in full-time positions and please refer to my linkedin page for more details or i would be glad to reply back as well.
SSI isn’t universally supported.
> no code systems let you hire cheap replaceable folk instead of highly paid technical folk

Until they don't, then you get to this point:

> just a few technical folk to clean up all the rubbish the others make

Which gets exponentially harder and more expensive as the size of the "no-code" codebase grows.

Going no-code for a startup is crazy. Your failure state isn't "it ends up being x% more expensive", it's that you hit a brick wall and you either rewrite from scratch (if you're small and agile enough), or your startup dies instantly (if you have enough users and competition that not delivering any features ever again isn't a viable strategy).

If I'm an investor and you're pitching a startup that's using no-code for anything other than a throwaway version for the purposes of a sales pitch, that's an instant dealbreaker. I don't care how good the idea is or how smart your team is, I'll happily bet the house on it failing.
I'm very happy about this. For a start Firefox Reality is the only way to view legacy WebVR content on a Quest (Oculus browser dropped support when they adopted WebXR).

Also it will hopefully support at least some extensions.

I just wish they would release a desktop VR build. There's a real gap there right now.
Just in case you were not aware, Python 3.6 reached end of life ~4 months ago: https://endoflife.date/python
> The disadvantage is low morale over time and lower quality products under the hood. Rotating workers who come in fresh can mitigate this outcome but at a cost.

Hehe the modern Agile software sweatshop.
The startup time of Emacs is not an issue because I only start the Emacs server once and keep it running for a long time, connecting the Emacs client to it as needed. Once the Emacs server is running then connecting to it is as fast or faster than starting vim from scratch. Even restarting Emacs from scratch can be effectively instant, if you don't have a giant config like I do. Vim startup time can be slow too, by the way, if you have a lot of plugins. So, effectively, vim and Emacs don't differ on startup time these days like they used to.

As to your question about Lisp, it definitely was a huge draw to Emacs because I fell in love with Lisp and almost the entire ecosystem of Emacs is written in Lisp... and I'd certainly much rather program in Lisp than vimscript, or even Python (or any of the other more mainstream languages).

I remember coming across various things I wanted to do in vim that were pretty awkward to do because of how clunky vim and vimscript were. Lisp and Emacs just made doing what I needed much easier overall (though some things were still easier in vim.. for example, vim has some powerful features in its regex engine that don't exist in Emacs, even when using Evil). This was before neovim, so maybe it's better there, though since both vim and neovim lack Emacs' Lisp ecosystem, I doubt they'll ever be able to match Emacs in this respect.

There were a lot of other reasons for the switch to Emacs, like having deep web browser and shell integration, being able to read my email from within Emacs, and do a ton of other things from it.. org-mode was another draw.
What do you think burns more fuel per passenger? A family driving the US's most popular truck vs. me alone driving in my Honda Jazz/Fitt?

https://www.carsized.com/en/cars/compare/honda-jazz-fit-2007...
Yup this has been a huge problem in Germany. Increasing transmission capacity between north Germany where all the wind resources are and south where the industry is has been fraught with obstacles by NIMBY's who don't like the power lines.
Thanks! It still a bit unclear to me but I'll dig more.
Cheers
I’ve been writing cross platform apps for many years now and a huge change that I don’t think people have noticed or understand is Cordova vs Capacitor. I put up with Cordova but always felt like I was on the edge of my builds breaking. The process to create the native project in the fly was always very inconsistent in my experience. The first debugging step for a failed Cordova app build was “try it again?”, that’s a horrible way to develop/live.

Then comes along Capacitor. I assumed “Ok, it’s just the newer version of Cordova”, I couldn’t have been more wrong. Things that were a huge pain with Cordova (building the native project from scratch, any changes to the native project for things like capabilities/permissions, the version of Google apis conflicting, etc) are gone. You now commit the Xcode and Android Studio projects to your source tree. This makes builds so much easier (throw fastlane into the mix and you’ve got something really awesome) and makes writing native code super easy.

I didn’t think I’d ever want to write native code for a cross platform app but Capacitor makes it stupid-simple to drop down to native code whenever you want. No more packaging your code in a plug-in (if you don’t want to at least), just add a class with the right annotations or extending the right class and you are calling native code from JS in no time at all. Native used to be scary or hard to work with in Cordova, that’s no longer the case in Capacitor. It gives me a ton of freedom and finally makes me feel in control of my builds and my app as a whole.

If you’ve slept on Capacitor I urge you to give it a shot, it’s quite nice to work with and fixes all the major pain points I’ve had over the years with Cordova.
80% of observed behaviours only reproduce 20% of the time.
No, I wasn't aware of that, thanks!
I can really see how you can get hooked by something like this.