"Hmm...I like when the assembler don't steps in my way and assumes that I know what I'm doing. Thats the reason why I don't like C, and prefer assembler. But when you like it, have fun!"
That quote about JavaScript is... huh. I do not understand how you can even begin coming to the conclusion of "JavaScript [is] utterly broken, incapable of executing the simplest programs without errors" when obviously, JavaScript (which I do not like, by the way) is productively used on a large scale (even back then), and constantly under scrutiny from programmers, computer scientists, language designers... it's just baffling.
It reminds me of when I was around 10 years old or so, maybe slightly older, and playing around with Turbo C (or maybe Turbo C++) on DOS. I must have gotten something very basic about pointers (which were new to me at the time) wrong, probably having declared a char* pointer but not actually allocated any memory, leaving it entirely uninitialized, and my string manipulation failed in weird and interesting ways (since this was on DOS without memory protection, you wouldn't get a program crash like a segmentation fault very easily, instead you'd often see "more interesting" corruption).
Hilariously, at the time I concluded that the string functions of Turbo C(++) must be broken and moved away "string.h" so I wouldn't use it. But even then I shortly after realized how insane I was: Borland could never sell Turbo C(++) if the functions behind the string.h API were actually broken, and it became clear that my code must be buggy instead. And remember, I was 10 years old or so, otherwise I don't think I would have come to that weird conclusion in the first place.
Nowadays, I do live in this very tiny niche where I actually encounter not only compiler bugs, but actual hardware/CPU bugs, but even then I need a lot of experiments and evidence for myself that that's what I'm actually hitting...
Sure, but “JavaScript [is] utterly broken, incapable of executing the simplest programs without errors” is a bit much. I find it hard to believe that even when I’m completely out of touch, I’d say that about a language that people are obviously productive in (as much as I hate JS myself).
Sometimes when I play a point n click adventure and I am stuck for hours on a puzzle I tend to think: I've tried everything... surely there must be some kind of bug for why I am not proceeding.
Only to then realize (after reading the walkthrough) that there was indeed a way.
I think it's human nature to find (rather search) blame not only in yourself but everywhere else... anyhow, since the author is reflective we should be forgiving as well.
Other languages have problems, but before some basic libraries (jQuery/Underscore) and language enhancements (Typescript/Coffeescript), it was arguably quite simplistic, and parts of the language were straight up anachronistic.
If you've ever been unfortunate enough to have to wrangle a VB script routine, it was (less bad) like that. If not, I would go find some assembly code and teach it yourself, and then imagine that instead of side effects in registers there were random effects on your code/visual state.
And like assembly code, you could now imagine that the same code might behave wildly different on different machines in different browsers.
So a bit of "old man"isms, but also I imagine his JavaScript was tainted by the early days. It's better in some ways now, worse in different ways, I don't mean to say that is the worst or the best, just to offer perspective on where it came from.
I’m well aware of all of those things (I program modern assembly for a living, and witnessed the evolution of JS), but the quote was “JavaScript [is] utterly broken, incapable of executing the simplest programs without errors”, which is a bit more extreme than what you’re describing.
Nobody said you should wait that long. As for your anecdote, what’s wrong with figuring out early during dating whether you plan on having children or not? People should talk about those things early, since there is hardly anything that makes a relationship more incompatible long term, and leads to more (even mutual) heartbreak and sorrow than having to break up with a person solely because their most uncompromisable life plan differs.
In my 20s, it felt indeed weird to bring that up early for me, because I wasn’t ready yet and didn’t even really know what I wanted yet. Later in life, when dating we always talked about potential family planning and general outlook on life early. (Unless it was never meant to be a serious relationship to begin with.)
This wasn’t even a first date, it was like she said hi to me at an event and just started taking about having a family.
Felt really awkward for small talk.
My point was the economy should support having a family in your 20s if that’s what you want to do. You shouldn’t need a well paid career, a quality lifestyle that supports a family should be available for everyone.
I imagine universal health care, paid family leave ( for months not weeks) and affirmative (free?) childcare could bring that gap.
At a point it isn’t even an age issue. A lot of people will never earn enough to really support a family, and that’s a failure of the social contract.
You should be able to get a job as a Walmart clerk, have your partner work part time and still afford to have a family.
I think I’ve muddled my own point here, but it should be easier. Maybe that Walmart clerk could own a house ?!
I do agree with your point about society. The reason we waited are way beyond monetary issues, and we would have waited regardless, but people should be able to support a family without an “advanced” career if they choose so.
I think it would be hard to find someone that does not agree with you on the street.
These conversations should not need to happen but they do because of the current inequality that exists. A couple can't change the world so they talk about these things since it's their best option
Society does kinda support this. People with low-paying jobs actually have the most kids. You just need more income if you want to have kids at a good time and send them to higher-end schools, including K-12.
Absolutely. It serves as a filter, if people are being honest. It also highlights the bizarre dating culture and view of life we've adopted. This dating culture has produced a good deal of rotten fruit.
The ultimate purpose of dating is to meet your future spouse. We're turned it into some kind of senseless sexual escapade, and this has poisoned the relations between men and women. It makes them exploitative and dehumanizing in spirit: sprinkling them with the waters of "consent" doesn't change that, as the subjective cannot abolish the objective. We've reduced sex to something that is merely pleasurable and contradicted its intrinsic and essential function which is procreative by employing an array of technologies that impede and interfere with healthy procreative processes. This creates a mindset not unlike that of a drug user who is obsessed with getting another hit with no thought given to the damage, or the bulimic who wants the sensual satisfaction of eating, but not the calories.
The psychophysical reality of sexual intercourse is much more than some passing physical pleasure. It mobilizes processes in us that are completely oriented toward bonding and the strengthening of the relationship in preparation for children. Whence the stereotype that men will often exit quickly in the morning after a one night stand with a strange woman? Because both can feel, if only subconsciously, that the processes of bonding are taking place, and who wants to bond — and in such a profound and intimate way — with someone they've just met? In this regard, the character of Julianna in Vanilla Sky makes an astoundingly profound and accurate remark for a movie coming out of Hollywood: "Don't you know when you sleep with someone, your body makes a promise whether you do or not?" Our capacity for sexual intimacy is likewise dulled.
(Masturbation is even worse. Those processes bond us with a fictional harem of the imaginary and close us within ourselves. For social animals like us, this is a recipe for misery.)
We thwart and ignore our biological nature to our own detriment. The procreative prime spans the mid-twenties into the early 30s. Statistically, most people should be having families by their mid-20s. Our culture confuses people and creates a pointless obstacle course that leads them to postpone such things either because they're too immature (and encouraged to remain so, also by this unserious dating culture) or because they believe they must achieve some arbitrary milestones first. Furthermore, family and community support has been dashed by a culture of hyperindividualism.
The causes of demographic decline are not a mystery. People simply either don't think deeply enough, or they don't want to make the cultural changes necessary to restore normalcy.
You have far too much of an obsession with sex here and really need to stop and take a breath.
Dating culture is evolved to help you find a mate based on YOUR choices and capability not your parents or class level. This allows you to “trial” compatibility over shorter time and find better fits.
What you seem to be talking about is 'Online Hookup Culture' which is more of a hobby if we are being honest than a way of finding a mate. And ultimately probably STILL better when faced with a society increasingly not finding mates or having kids at all. So basically all of your thoughts are self-contradictory due to a bit of self righteousness here.
Please don’t let your hangups around sex (correct or not) become a world view. It’s not a healthy obsession.
This is a much more reasonable position than many will believe. I think writing like a 19th century nonfiction author probably contributes to that aha
Edit:
To be clear I appreciate this comment and agree with it in the large. It’s hard to talk about these things without being quickly dismissed in the current zeitgeist.
Sexual escapades are only senseless if you rigidly believe sex is only for specific things, and adopt a model where human beings are property and can be owned. While sex does have a biological purpose, that in itself doesn't mean it has to be limited to that purpose.
Sex is fun and most sex doesn't lead to procreation, nor is intended to. The last 50 times I've had sex, me and partner(s) involved have had no intention of making a baby, and that's fine. Nature/God agrees with me, because the number of children most families have are typically far less than the number of times the parents have had sex.
There's a lot of times people want sex and don't want it to be some big life changing event. I won't marry someone like that.
> This creates a mindset not unlike that of a drug user who is obsessed with getting another hit
Everyone wants pleasurable things with a minimum of bad or unwanted consequences. This is called being smart and using your God-given brain and free will. This doesn't make anyone a drug user. This puritanical war on pleasure can only serve authoritarian and anti-human ends, which is often an explicit or implicit base of forms of slavery/indenture, and is the main reason why I strongly advocate against it.
> The psychophysical reality of sexual intercourse is much more than some passing physical pleasure.
Anything that feels really good will beget attachment because you want more of it. When it's attached to a person, you're going to want to be around that person more. And of course, human beings are naked apes with courtship and bonding instincts and all that good stuff. But people bond over things other than sex, and any good relationship or marriage will have many bonds other than the sexual one. Indeed, marriages where sex is the only reason they got together are as hollow as this drug user strawman you trotted out.
> Masturbation is even worse.
People who become overly dependent on parasocial relationships with fictional anything, whether that's a harem, video game, movie star, person mentioned in a religious book, etc. need help. I masturbate from time to time and it does not give me any problems, but I'm not addicted to it. But I would rather lonely people masturbate themselves into a coma than sexually assault others simply because of people who will say masturbation is wrong but at the same time won't consider other things like legalizing prostitution.
> they don't want to make the cultural changes necessary to restore normalcy.
I don't. The old way sucked. Robots and AI should be doing all our menial work, and the possibilities for pleasure are endless. The people who just can't exist without an employer giving them meaning because they never got enough approval from their daddies need to move to another planet.
I did not have more time in my 20s. In my 20s and early 30s, I was busy “getting out there”. Building my life, my interests, my foundation (not just my career). Now I have a happy life to stand on, and can devote more time, attention, and energy to my family.
I don’t deny that your way can work out as well. But OPs advice was “get children before you are 30, don’t wait until after”. Whereas my honest advice, based on my experience, is “wait until you are 35, you’ll be much more stable life in several regards”.
Which approach is best for you depends on a lot of things. For me, I can honestly say, there is no way I would be where I am if I had had kids in my 20s or even early 30s, and I also wouldn’t have been as good a father as I am right now based on how I’ve grown since then. Both things that my child directly benefits from.
I was “getting out there” too! So many major life milestones. But actually it has never stopped. Most of my major career changes happened after the second child. I have entirely new interests now.
I feel like I do have the unique perspective having actually done both. I don't need to assume what kind of parent I was in my 20s because I was that parent. And I'm a different parent now. But being a younger parent was a great experience despite any other consequences.
That’s interesting. Because I genuinely feel I’m much better cut out to be a parent now. Is it different for you? I have so much patience and understanding, and I see that lacking in many of the younger parents around me. I see them and I remember myself.
And the life I have would just not have been possible if I had a child back then. Not even if I completely sacrificed family time and attention back then, which I never would have wanted.
But I guess we have to agree to disagree. For you, being a younger parent worked out better. For me, I’m certain I got my child at the right time. In any case, I find OPs general recommendation that if you want children, you should have them by 30, to be ill-advised to the point of being harmful. Many people would benefit from waiting until later.
I'm 32, and I think I currently have much less patience and understanding than I did at say 22. Life has basically broken me to the point that I simply don't have the capacity for these things that I used to.
Haha, I like to joke that I reached peak intellectual capacity around 26 and peak emotional maturity around 14 and both have been dropping from their peak since then.
It also depends on the person. I was not an adult at 27. I realized I was one at 32 though.
Kids at 27 would have been a bad bad idea. Kids at 32 as well (wrong partner). I’m even older now but I am with the right partner and naturally want kids now. Before her, the topic wouldn’t even cross my mind.
I think it’s really hard to give general advice if one doesn’t mention how their advice interacts with other variables
The advice was to start before you are 30, not finish then. If you have multiple kids my advice is the last should be around 35 maybe 40 but space them out
We did wait for the “perfect” time, and are very happy we did.
I got my son at almost 40, and I’m positive I’m a much better parent because of that. Sure, kids cost energy, but at 40 and 50 you’re not geriatric. I often get the opportunity to compare our parenting style to younger parents, and it’s clear that they often have some emotional growing up to do themselves. They complain about normal parenting things that we just shrug about, they are torn between their career and raising a kid, and most importantly they often lack patience, where to us it just comes natural.
> they often lack patience, where to us it just comes natural.
Having kids fast-tracked me to a critical increase in patience. I've grown so much in less than three years because of my kids. I'm not sure this growth would have ever happened so quickly through other means.
And I'll always have a special, particular respect especially towards my firstborn for causing that in me, and for enduring my shortcomings in the meantime.
My wife and I had our first at age 15. Then another at 22. And our last at 27. I've raised children while on welfare and while a software engineer.
I was more patient as a teen than I am now in my 40s. Now I am tired. All the time. I fear I would literally die of exhaustion if I had to maintain more irregular hours than I already do due to insomnia that I have developed over the last half decade.
I didn’t say get pregnant at 50. I said I became a parent at almost 40, my wife is a couple of years younger. No problems whatsoever, and I seem to have more energy for parenting (and especially patience) than the parents in their 20s who haven’t even found themselves yet.
Paternal age is also a contributor. Children with fathers over 40 see an increase in potential diseases, a shorter lifespan and higher infant mortality, likely due to DNA mutations.
According to that page, the whole issue seems to be very nuanced. It also contains the quotes I attached below.
Be it as it may, I conclude that there is an elevated risk for problems the older you get (although for some issues, cause and effect may be reversed, which is hard to resolve), but that that risk may not be so significant as to outweigh other advantages.
> A simulation study concluded that reported paternal age effects on psychiatric disorders in the epidemiological literature are too large to be explained only by mutations. They conclude that a model in which parents with a genetic liability to psychiatric illness tend to reproduce later better explains the literature.[9]
> Later age at parenthood is also associated with a more stable family environment, with older parents being less likely to divorce or change partners.[43] Older parents also tend to occupy a higher socio-economic position and report feeling more devoted to their children and satisfied with their family.[43] On the other hand, the risk of the father dying before the child becomes an adult increases with paternal age.[43]
> According to a 2006 review, any adverse effects of advanced paternal age "should be weighed up against potential social advantages for children born to older fathers who are more likely to have progressed in their career and to have achieved financial security."[63]
It seems kids procreated by older parents (aged 35 years or older) have increased risk of Down Syndrome. The effect is most pronounced when both parents are older than 35 years: https://pubmed.ncbi.nlm.nih.gov/12771769/
It's for people that want to use the Windows Terminal to edit files. The old `edit` command has been unsupported on Windows since 2006, so there was no Microsoft-provided editor that could be used in the command line since then.
Who's editing files big enough to benefit from 120GBps throughput in any meaningful way on the regular using an interactive editor rather than just pushing it through a script/tool/throwing it into ETL depending on the size and nature of the data?
I work exclusively outside of the windows ecosystem, so my usual go to would be to pipe this through some filtering tools in the CLI long before I crack them open with an editor.
"Better tools for the job" isn't always "the tool currently bringing in the $$$$$$$$$$$$$$$". So you live with it.
Sure, maybe by switching to linux you can squeeze out an extra CPU core's worth of performance after you fire your entire staff and replace them with Linux experienced developers, and then rewrite everything to work on Linux.
Or, live with it and make money money money money.
To turn this around, you can have fun and ask if something is meaningful or not outside the fun at the same time. If it is, great. If it's not, no harm.
I'm not saying that doing this can't be fun, or even good to learn off of, but when it's touted as a feature or a spec, I do have to ask if it's a legitimate point.
If you build the world's widest bike, that's cool, and I'm happy you had fun doing it, but it's probably not the most useful optimization goal for a bike.
Not a great analogy. This editor is really fast. Speed is important, to a point. But having more of it isn't going to hurt anything. It is super fun to write fast code though.
Not on the regular, but there are definitely times I load positively gigantic files in emacs for various reasons. In those times, emacs asks me if I want to enable "literal" mode. Don't think I'd do it in EDIT, though.
As a specific benchmark, no. But that wasn't the point of linking to the PR. Although the command looks like a basic editor, it is surprisingly featureful.
Fuzzy search, regular expression find & replace.
I wonder how much work is going to continue going into the new command? Will it get syntax highlighting (someone has already forked it and added Python syntax highlighting: https://github.com/gurneesh9/scriptly) and language server support? :)
Right, these are more useful features, IMO, than the ability to rip through 125GB of data every second. I can live without that, but syntax highlighting's a critical feature, and for some languages LSP support is a really big nice-to-have. I think both of those are, in this day and age, really legitimate first-class/built-in features. So are fuzzy searching and PCRE find&replace.
Add on a well-built plugin API, and this will be nominally competitive with the likes of vim and emacs.
My guess would be there are some people at MS who, somehow, still can do something fun. Because they are not assigned on the another project on how to make OOBE even more miserable.
/rant Today I spent 3 (three) hours trying to setup a new MSI AIO with Windows Pro. Because even though it's would be joined to the local ADDS and managed from there - I need to join some Internet connected network, setup a 3 stupid recovery questions which would make NIST blush and wait another 30 minutes for a forced update download which I cannot skip. Oh, something went wrong - let's repeat the process 3 times.
Yeah ... I don't think there's any overlap between "users largely unfamiliar with terminals" who want something easy to use, and 'Linux users who are sufficiently technical that they would even hear about this repo'.
Here's a scenario. You're running a cluster, and your users are biologists producing large datasets. They need to run some very specific command line software to assemble genomes. They need to edit SLURM scripts over SSH. This is all far outside their comfort zone. You need to point them at a text editor, which one do you choose?
I've met biologists who enjoy the challenge of vim, but they are rare. nano does the job, but it's fugly. micro is a bit better, and my current recommendation. They are not perfect experiences out of the box. If Microsoft can make that out of the box experience better, something they are very good at, then more power to them. If you don't like Microsoft, make something similar.
> You're running a cluster, and your users are biologists producing large datasets. They need to run some very specific command line software to assemble genomes. They need to edit SLURM scripts over SSH. This is all far outside their comfort zone. You need to point them at a text editor, which one do you choose?
Wrongly phrased scenario. If you are running this cluster for the biologists, you should build a front end for them to "edit SLURM scripts", or you may find yourself looking for a new job.
> A Bioinformatics Engineer develops software, algorithms, and databases to analyze biological data.
You're an engineer, so why don't you engineer a solution?
The title is a bit confusing depending how you read it. Edit isn't "for" Linux any more than PowerShell was made for Linux to displace bash, zsh, fish, and so on. Both are just also available with binaries "for" Linux.
The previous HN posts which linked to the blog post explaining the tool's background and reason for existing on Windows cover it all a lot better than a random title pointing to the repo.
PowerShell lends itself really well to writing cross-platform shell scripts that run the same everywhere you can boot up PowerShell 7+. It's origins in .NET scripting mean that some higher-level idioms were already common in PowerShell script writing even before cross-platform existed, for instance using `$pathINeed = Join-Path $basePath ../sub-folder-name` will handle path separators smartly rather than just trying to string math it.
It's object-oriented approach is nice to work with and provides some nice tools that contrast well with the Unix "everything is text" tooling approach. Anything with a JSON output, for instance, is really lovely to work with `ConvertFrom-Json` as PowerShell objects. (Similar to what you can do with `jq`, but "shell native".) Similarly with `ConvertTo-Json` for anything that takes JSON input, you can build complex PowerShell object structures and then easily pass them as JSON. (I also sometimes use `ConvertTo-Json` for REPL debugging.)
It's also nice that shell script parameter/argument parsing is standardized in PowerShell. I think it makes it easier to start new scripts from scratch. There's a lot of bashisms you can copy and paste to start a bash script, but PowerShell gives you a lot of power out of the box including auto-shorthands and basic usage documentation "for free" with its built-in parameter binding support.
I dunno, I spent a lot of years (in high school at least) using Linux but being pretty overwhelmed by using something like vim (and having nobody around to point me to nano).
EDIT.COM, on the other hand... nice and straightforward in my book
There's no shortage of less technical people using nano for editing on Linux servers. Something even more approachable than that would have a user base.
Especially noting it's a single binary that's just 222kb on x86_64— that's an excellent candidate to become an "installed by default" thing on base systems. Vim and emacs are both far too large for that, and even vim-tiny is 1.3MB, while being considerably more hostile to a non-technical user than even vim is.
I can definitely see msedit having a useful place.
What do you mean, you don't want "software"? Where do you draw the line? A basic digital wristwatch has "software".
You're going to have software for a modern, efficient car, whether you like it or not. For the engine (fuel injection alone needs a bunch of software), ABS, traction control, A/C, and countless other things. And whether your radio has physical buttons or not, unless that physical button is on a radio from the 1980s and directly controls a variable capacitor and a belt to a frequency indicator, it's going to have software.
Of course we had cars entirely without software, about 50 years ago. But they were slow, had many quirks, and absolutely massive relative fuel consumption compared to today.
> What do you mean, you don't want "software"? Where do you draw the line? A basic digital wristwatch has "software".
I think this nomenclature is a result of the post-Jobs software as "app" paradigm + Web as the definitive "application" platform era.
The majority of software written, especially in these circles, is going to be some sort of user interface/CRUD stuff. The "invisible" (and frankly remarkable, when talking of things like ECUs and ABS software) is basically like The Earth (it's just always been there and taken for granted).
LSPs should work fine with TRAMP. In practice I have a problem with it, since there is some bad interaction between eglot, TRAMP, and clangd in certain cases, but that is a specific situation and a bug.
gopls was a bit of a pain. By default it uses stdio, and there were some integration issues with eglot, tramp, amd gopls. I also had some issues trying to use tcp ports. I switched to terminal emacs over ssh, the. use distrobox (I didn’t want to install dev tools locally).
reply