skysight-inc/HackerNews huggingface dataset:
> That's Luddite bullshit. Complete gibberish.

I would recommend you to read the guidelines when posting here.

https://news.ycombinator.com/newsguidelines.html

> The simple fact is that fuel cell cars are also EVs. As a result, there are no fundamental limitations compared to BEVs. They are fundamentally guaranteed to be just as good as BEVs.

In other words, you pay for two cars in one when you could simply pay for one car and charge it from any wall outlet.

> And since BEVs are not a sustainable technology

This is a statement which requires proof.
exactly this.

it is easier to sort out alternatives if i am already close to the destination. when i have transfers near the start i have to be very careful to ensure that i don't miss the main part of the trip. where as i often don't even bother to look up transfers at the destination until i arrive. i'll just take whatever is available.

on a recent long flight where i was in a different city than the airport i actually spent a night in the airport city to avoid troubles on the way to the city.

but the problem in the article seems to be just about this: very inflexible transfer options at the destination.
[Old school JS developer reading the article and suffering PTSD and flashbacks]

I must not fear.

Fear is the mind-killer.

Fear is the little-death that brings total obliteration.

I will face my fear.

I will permit it to pass over me and through me.

And when it has gone past, I will turn the inner eye to see its path.

Where the fear has gone there will be nothing.

Only I will remain.

[Finishes reading the article and realizes they survived, but now all sweaty]
Which "two" authors?

Perl continues to flourish into its fourth decade thanks to a vibrant community of users and developers. The following people are known to have contributed the improvements that became Perl 5.38.0:

Alex, Alexander Nikolov, Alex Davies, Andreas König, Andrew Fresh, Andrew Ruthven, Andy Lester, Aristotle Pagaltzis, Arne Johannessen, A. Sinan Unur, Bartosz Jarzyna, Bart Van Assche, Benjamin Smith, Bram, Branislav Zahradník, Brian Greenfield, Bruce Gray, Chad Granum, Chris 'BinGOs' Williams, chromatic, Clemens Wasser, Craig A. Berry, Dagfinn Ilmari Mannsåker, Dan Book, danielnachun, Dan Jacobson, Dan Kogai, David Cantrell, David Golden, David Mitchell, E. Choroba, Ed J, Ed Sabol, Elvin Aslanov, Eric Herman, Felipe Gasper, Ferenc Erki, Firas Khalil Khana, Florian Weimer, Graham Knop, Håkon Hægland, Harald Jörg, H.Merijn Brand, Hugo van der Sanden, James E Keenan, James Raspass, jkahrman, Joe McMahon, Johan Vromans, Jonathan Stowe, Jon Gentle, Karen Etheridge, Karl Williamson, Kenichi Ishigaki, Kenneth Ölwing, Kurt Fitzner, Leon Timmermans, Li Linjie, Loren Merritt, Lukas Mai, Marcel Telka, Mark Jason Dominus, Mark Shelor, Matthew Horsfall, Matthew O. Persico, Mattia Barbon, Max Maischein, Mohammad S Anwar, Nathan Mills, Neil Bowers, Nicholas Clark, Nicolas Mendoza, Nicolas R, Paul Evans, Paul Marquess, Peter John Acklam, Peter Levine, Philippe Bruhat (BooK), Reini Urban, Renee Baecker, Ricardo Signes, Richard Leach, Russ Allbery, Scott Baker, Sevan Janiyan, Sidney Markowitz, Sisyphus, Steve Hay, TAKAI Kousuke, Todd Rinaldo, Tomasz Konojacki, Tom Stellard, Tony Cook, Tsuyoshi Watanabe, Unicode Consortium, vsfos, Yves Orton, Zakariyya Mughal, Zefram, 小鸡.
> Interestingly, AI might change this. Not that it would be a good idea to write everything in assembly, but at least it would be possible now.

More likely to be the opposite IMO. AI could make the Sufficiently Smart Compiler a reality; maybe autovectorization will finally work and you could write FizzBuzz in Python and it would perform like this.
PHP is "worse" in these respects when compared to other mainstream languages, yes - we can probably grant that, although it's not as bad as it once was.

Perl is just one big game of code golf. There is absolutely an entire era of developers who looked at that and ran far away (and I do not blame them at all).
I recommend to use qx instead of backquotes. Much more readable because with some fonts backquotes are almost invisible.

https://perldoc.perl.org/perlop#qx/STRING/
Again you're making this up. That's not what the message reads. It literally says the future of Nim is assured because there is both funding and people working on it. He says he doesn't want to partake in community building because ...stuff happened with the diversity mob. It turns out that they've been preaching acceptance while harassing people with different upbringing online.
Right ok I misunderstood I thought you meant physically can't cross rather than not permitted, yes that is correct!

However if you stand at the Albert Bridge (which is the one you meant with that width restrictions) you'll see tonnes of LR and RR going through which are wider than that as well as Sprinter vans which are about the same as the X... I can only assume the police take the view that if you fit through the width restriction (which must have some leeway on them as bigger LRs are about 81") they won't bother you...?
This might be a controversial opinion, but I think if anyone deserves to charge enterprise clients for API it should be Wikipedia.
I'm guessing they mean the two folk listed in the AUTHORS section of the `perlclass` page:

https://perldoc.perl.org/5.38.0/perlclass#AUTHORS
This entire comment section is a bit of a dumpster-fire. I'm convinced the word database has outlived its usefulness for any serious discussion. It has the informational density of saying : "I work in IT"
“As a hacker?” What does that mean? I write code and administer systems for a living, but I think of that as a job, not an identity. My “happiness” has very little to do with my job, probably because I treat it as a source of income rather than my identity.
They meant "many important and/or well known" - some things go without saying. They didn't meant to include INTERCAL or BRAINFUCK or OZ.
In practice, hot code reloading and mnesia are pretty cool concepts but very far from trivial. The vm and OTP provide mechanisms to work with such advanced concepts, but it still requires an intense amount of discipline and process to execute effectively.

Consider hot code reloading to be like changing the tyres on a moving car, the pieces and tools are there to make it possible, but in almost every situation it's more sensible to stop and change. Backwards compatibility for all API changes, code correctness and deployment methodology need to be fixed before you can start a hot rollout. That's not even to consider a flexible application architecture that will be compatible with such changes in functionality (OTP does indeed ensure this is compatible on the basic process level, but there is no magic bullet around high level architecture).

For given hard requirements, e.g. upgrading the application without dropping TCP connections - this can be a killer feature that removes considerable development effort, but usually it's a very cool thing that you don't need.

That being said, hot code reloading on the individual module level I have found to be a useful and dirty trick to change the behaviour of running applications (add log statements / telemetry where they weren't before to diagnose production issues). This still has all the caveats and danger of the above, but is more limited in scope.
Can someone explain the rationale for not being able to call a static method on an instance?
A lot of programming language do this, I assume there is a reason, but I don't understand what it is.
Was it really not possible to make that a shorthand for the existing structure with blessing variables? Having two object systems may make things too confusing.
Could be a cultural NIH syndrome. :)
> Other countries desperately want to be the next US.

Americans still think it’s 2005 huh.
I'd like your feedback and opinion please.
Ask HN: What software might be a necessity in the future?
I have free time to spare. I have technical knowledge and have built production web apps for companies as well as myself. I want to invest this time to build something which may possibly be impactful to someone or the other in a meaningful way. I am out of problems which I can think of so if you have any interesting problem, difficulty, or idea, let's discuss
Electric cars have a lot more problems than range.

Toxicity and pollution of producing the battery is an immediate one. And the fact it's junk in 5-6 years, obsoleting often the entire car (or requiring an extremely expensive replacement).

The fact BEV are much heavier and are wearing down the roads much faster.

And while ICE are of higher risk of a fire, an ICE fire seems like child's play compared to a BEV fire. This thing is impossible to put out and turns everything around to fine (and very toxic) dust (including, again, the road below).
GDB on its own does a reasonable job debugging python: https://wiki.python.org/moin/DebuggingWithGdb
Chicken & Egg problem, the reason the web is so flooded with SEO-ed crap content is because of Google Search.
And sadly the same (case insesitivity, not shouting) is the case in Nim today, iirc
You can call a static method on an instance. This project allows you to call static methods not defined within the instance's class.
The move towards AOT is mostly for lower startup times and lower memory usage, not to make the application faster in general.
Since about 2008-01 or so, using Moose, we've been able to do something like:

{ package Point;
use Moose;
has 'x' => (is => 'ro', isa => 'Int', required => 1);
has 'y' => (is => 'ro', isa => 'Int', required => 1);
sub as_string {
my $self = shift;
return sprintf '(%d,%d)', $self->x, $self->y;
}
}
my $origin = Point->new(0, 0);
say $origin->as_string;
> In the end the goal of Buddhism is not to change outer conditions but to get to a state were hapiness is experienced regardless of outer experiences.

I would argue not trying to change the outer conditions is an extreme view, which is a notion rejected in Buddhism ;-)

Some things can be changed, like keeping your environment clean. You can, of course, simply find happiness regardless of the state it's in - clean or filthy - but you're kidding yourself, and only yourself, if you believe you won't be happier if it is clean(er). Therefore, you can find (more) happiness by changing the environment you're _but_ also excepting that it will get dirty again, requiring you to clean it again.

All this being said, neither of us is right or wrong. That's sort of the point.
To decompress, enjoy nature, leave the dog free to run around and chill on a hammock with a good book.
I don't think range is really the issue. If charging stations were as prevalent as gas stations, and charging time was much lower, that'd probably be sufficient for most people.
There's even one for 8-bit Ataris:

Interlisp[28] – developed at BBN Technologies for PDP-10 systems running the TENEX operating system, later adopted as a "West coast" Lisp for the Xerox Lisp machines as InterLisp-D. A small version called "InterLISP 65" was published for the 6502-based Atari 8-bit family computer line. For quite some time, Maclisp and InterLisp were strong competitors.
Nah, "everything is slow" is vanishingly rare in practice.
I don't think the world needs one more walled garden.

But, instead of commenting on a URL, what if you could comment on a snapshot in the Wayback Machine on The Internet Archive by using that link instead. And then make a hash of that link and post your comments (and search for others' comments) on an open platform like NOSTR?

The building blocks already exist today.

Here is an example: https://snort.social/e/nevent1qqsytrx2ya4854mvhz5tvpwzutvdlf...
Ehh, ive been talking about whole lang and ecosystem

But I agree about "this" being similar concept
We must live in the Walternate universe where it takes a million lines of Java to do next to nothing at all.
And if someone said that vacuum tubes are the future, what is your response? It's pure absurdity to claim that an obsolete technology is the future. You'd immediately get up and ridicule the obvious non sequiturs in their logic. FYI, BEVs predate the ICE car. It is an incredibly outdated idea.

In reality, hydrogen cars are far cheaper to make than BEVs. They have very little raw material needs. They do not need the hundreds of kilograms of batteries that BEVs need. They only need water as their raw material. That's fundamentally a superior idea. You can never make a coherent argument that an EV powered by rare or limited resources could ever be a better idea.

Again, a fuel cell car is literally an EV, only one whose "battery" is made from water. You cannot do better than that.
I think most have realized by now that self-driving is not a serious possibility anytime soon for anything other than a nice option to upsell the car by some small margin.

And Tesla FSD is not even best-in-class between car manufacturers (Mercedes is, with actual approved and shipped commercial L3), not to mention the entire self-driving market (where Waymo is way ahead).
You might be interested in the p2p design of Peergos. You sign up to Peergos[0]. Your initial server is just responsible for storing your data (although you can run as many live mirrors as you like), and clients verify all updates. You can automatically move server (by running a command) and all your data is moved, and old links continue to work, and you keep your social graph and identity.

You can also log in through any instance, including localhost. Links also work on any server because they include a capability to the content in the link.

This is the beauty of content addressing plus public key based addressing.

[0] https://peergos.org
It is relatively convincing when there are plentiful free alternatives and no one is telling you what to use (This from an emacs user).
There's no point in having 4K res if your lens isn't sharp enough. Just sayin'...
Exactly, moreover... His comment

> I was specifically talking about sexual violence.

Makes it clear that he tried to move the discussion away from recognizing civilian suffering and opposing the countries which oppressed most of the world with their military force first... Towards just trying to make a case for Russia to be "more brutal", regardless of factual accuracy. For some people, stoking outrage takes priority.

It's not the first time that the propaganda is trying to scaremonger about a "horde from the east":

https://redsails.org/hordes-of-rapists
Simula still is less forgotten than its successor BETA.
I don't see manufacturers agreeing on a standardized battery pack size and shape. I also don't see battery swap stations getting built to the density needed, even if only as a supplement to charging stations. Battery swap stations would be significantly more expensive to build and maintain than charging stations.

Regardless, we don't have battery swap, and I don't think any (serious) manufacturers have plans to go that route, so it's a moot point.
It’s always been a write-only language.
Cheers! Yes, I already have 'it's' and 'it’s', but that one escaped! Added now.
Bringing capacity online takes years of planning , it is quite possible that market conditions no longer support that kind of growth (recession/more competition etc).

Tesla has very aggressive capacity being built in Texas , Mexico, Berlin and Shanghai not to mention other component plants in Nevada, Canada Netherlands etc.

It is quite probable next year they cannot keep growing sales aggressively as before and some capacity will idle despite breaking records and hitting targets and having more unsold inventory .
Thanks a lot for the exposition. I'll take these to heart. Not sure about Minecraft yet (despite your praise) due to the open-ended nature and the possibility to get addicted, but the NES/SNES Mario games I'm sure to try (I have a RetroArch setup). They should get tired of that by themselves easily, and get improved hand/eye coordination that should help them onboard to Minecraft in a year.
The one from my earlier comment is a meta study, so it bears more weight.
I'd like to see some actual photo comparisons from this camera.

"4K photo" means absolutely nothing except the pixel count. There could be a 32x32 photosensor and software upscale to 4K. The lens could be made of recycled Styrofoam.
I might be a minority voice here, but I support this, because they stop all of these initiatives, not only pride month. Companies should not have to need a public opinion (be it pro or contra) on all topics, especially if it is not related to their field of work.
No. Well…it’s complicated.
https://en.wikipedia.org/wiki/Citro%C3%ABn_Ami_(electric_veh... (~$11k)

EVs aren't inherently expensive, the issue is that the industry tends to advertise and equip EVs as a status symbol and price them as a luxury, rather than focus on simple/cheap designs that would have more impact on emissions.

That's not only EVs, the way the industry pushes SUVs is also painful. But it's really annoying to see what could be a great improvement wasted with regards to the challenges we're facing.
... which you created when none of the other stacks existed, and stood behind for 20 years while all your competitors changed their mind about everything every couple of years.
Notice that they are talking in the present tense, while you are talking in the past tense.
> At the very beginning, this web browser started under the name "Netscape", and JavaScript didn't exist yet. Mozilla forked out of Netscape in 1998, and there was little JS in the source code at this time.

I have no idea what point you are trying to make here. Firefox—not Netscape—has been a JS-driven app since its very first day of existence. (Netscape Navigator 6.x, which has nothing to do with Netscape of the early-to-mid 90s, is the same way—but that's beside the point: I said Firefox, and that's what we're talking about.)

> Firefox doesn't use the standard bundlers of the Node ecosystem, but it's because it has its own build systems and bundlers. It's a beast that needs 30GB of disk to compile, with a custom build system written in shell, Perl and mostly Python, with many tests systems (including for "mochitest" JS code).

I don't know what Firefox's build system looks like now, but at the time that Node debuted (2009), Firefox 3 was the latest release, with Firefox 4 development underway. It did have (and always had) a pretty gnarly build system made of shell scripts, Perl, autotools, et cetera... the same as almost anything that involved reliably compiling a large project with C/C++ across many distros (not to mention other platforms), which was the entire reason behind it. The use of JavaScript, however, had nothing to do with that; there were no JS bundlers. You brought symbols in scope by adding a script element. You still can.

This is also how WebKit's inspector is written to this day, last I checked (~6 months ago or so).

> JS was notoriously designed and implemented in a rush

Again, no idea what point you're trying to make here. JavaScript was done in a rush. It's also thoughtfully designed—certainly more than it gets credit for—and more than other languages that had more time (and less of an excuse). And it remains pretty nice, popular misconceptions notwithstanding (and not helped by self-loathing/self-sabotaging developers from the GitHub era like the author of the submitted article).

> But it doesn't scale. For a complex code, I want a linter, I want automated tests and coverage, I want to split the source code over many files... NodeJS is the standard requirement for all of these.

Hard to cover this succinctly given how much weird stuff is packed in here.

Hundreds of thousands of lines of code of higher quality (and subject to harsher requirements) than the Node fanclub has ever produced is proof that JS scales.

Testing is a basic engineering concern and common across the industry and across all languages. It's a completely orthogonal issue.

Lint as much as you like if that's what you want. Neither Node nor the Node way of development are in any sense a requirement.

For having source code "split [...] over many files", whether you use Node or not (or follow their fads) is neither here nor there...
This is the Internet version of the tragedy of the commons: https://en.wikipedia.org/wiki/Tragedy_of_the_commons

So many people and groups want to profit with as little effort as possible that the commons (freely available data, open APIs, FLOSS software, etc.) is being overrun with little to no regard for the long term effects.

Data can be copied endlessly, but it has to be generated the first time and updated or else it becomes stale and its usefulness decays. If no one is willing or able to generate or update it, there is nothing good and the signal-to-noise ratio falls off sharply. Everything is noise and it sucks.
It's interesting that this somewhat implies the notion of a heap and garbage collection, but that this was not considered for strings.
they already do.

https://en.wikipedia.org/wiki/Wikimedia_Enterprise

https://enterprise.wikimedia.com/
is that gpt-4 (with a paid subscription to chatGPT?) The difference is quite massive when it comes to hallucinations
I agree with the article; GPT is not AGI, it's ABSI (automated BS intelligence). That's certainly useful and it will automate some jobs, but a) it's just an enabling technology for new applications, b) we haven't seen these applications yet, so we have no real idea what the impact will be.

To put it another way: the enabling tech for iPhone was (mainly) multitouch capacitive displays. I dont think anyone predicted Uber or taxi drivers being at risk because of multitouch when it was unveiled (late 90s?), but here we are.
This is the key sentence, IMHO:

> Once confirmed to have no ill effects on the human body, it will be aimed at treating children aged 2 to 6 who exhibit anodontia.

This greatly limits usefulness of the whole enterprise. The problem is that this condition is not likely to be found at that age, it's found later when the problem is evident to parents. What is actually needed is some treatment for teenagers or young adults.
Yes, it does. Even my podunk little credit union's app works absolutely fine.
> such as the ability to embed a shell command in backquotes and get its output easily.

Unless thing have changed in the last 20 years - and they might well have! - that was also a very error-prone tool.

For example, filenames may have spaces in them, but most don't. Experience shows that people forget about that possibility during development and testing. But backticks parse the string after interpolation, causes the spaces to be interpreted as distinct terms.

Here's an example using backticks to call md5sum to compute the MD5 of the empty file "test.txt":

% touch "test.txt"
% perl
$fname = 'test.txt';
$a = `md5sum $fname`;
print("Got: $a\n");
^D
Got: 8b8db3dfa426f6bdb1798d578f5239ae test.txt

Looks good, right? Now try it with "test me.txt":

% touch "test me.txt"
% perl
$fname = 'test me.txt';
$a = `md5sum $fname`;
print("Got: $a\n");
md5sum: test: No such file or directory
md5sum: me.txt: No such file or directory

This leads to all sort of fun (in the sarcastic sense) when people use variable names with shell metacharacters:

% touch 'test.txt|echo hello'
% perl
$fname = 'test.txt|echo hello';
$a = `md5sum $fname`;
print("Got: $a\n");
Got: hello

There are ways to avoid this, but as the FAQ points out at https://perldoc.perl.org/perlfaq8#How-can-I-call-backticks-w... , the solution is to avoid using backticks. (The example there is of passing an arbitrary search string to grep, without dealing with shell expansion.)

You might be interested to know Julia's take on the same operation. It parses the backtick-quoted string itself (without a shell), and handles interpolation in a shell-like way, with awareness of the underlying variable (eg, string, or enumerating a list or Cartesian product of strings). The result is a Cmd object, which can be passed to other functions to describe how to use or process the Cmd.

See https://docs.julialang.org/en/v1/manual/running-external-pro... .