HN user

chmln

738 karma
Posts6
Comments217
View on HN

That whole example feels like a strawman, from my (maybe limited) experience something that's rather the exception than the norm.

First, lifetimes are elided in most cases.

Second, the curly braces for the closure are not needed and rustfmt gets rid of them.

Finally, the "map" on result can be replaced with a return statement below.

So, in the end we get something like:

  Trying::to_read(syntax, |like| this.can_be(maddening))?; 
  Ok(())

One of the most common use cases for the `ctrl` key is COPYING shit and followed by PASTING shit and it DOES NOT WORK in a fucking TERMINAL... Because `ctrl-c` sends an interrupt

Most terminals today have a copy-on-select feature, which means you don't need to ctrl-c at all. Just select and ctrl-v.

Almost every point made here is basically false.

The best performing languages are imperative (C, C++, Rust), with functional languages being at least an order of magnitude slower both in benchmarks and real-life workloads. Whatever properties were supposed to make it faster/parallelizable have clearly not manifested themselves very well after decades.

Imperative and parallel code also does not have to be a nightmare at all, as evidenced by Rust and even Go.

Immigration has a direct impact on the labor market. Unlimited migration would likely outpace any sort of economic growth and massively depress wages. I would not look forward to competing with an order of magnitude more candidates for jobs with mediocre pay.

Your comment serves as an attempt to change the subject

That's funny because you did not refute anything I said and just brought up Trump, whose opinion I couldn't care less about.

That's definitely true as well - some responses by poettering in systemd issues in particular are unnecessarily condescending and very unprofessional.

Also, while systemd and pulseaudio were heavily pushed by many distros, alsa was and still is an option and systemd alternatives exist for those who care that much.

This is practically the end of Mozilla, a sad result of horrendous mismanagement. Instead of pouring all its resources to make a superior browser and thus attract more money by having bigger market share, they just stagnated. They bought pocket and gutted Servo for virtual reality. They invested in superficial political activism and paid exorbitant amount of money to execs.

Firefox is inferior in all regards except privacy. People will claim it's just as fast as others, but even if it wasn't obviously false it wouldn't be enough. It should be undoubtedly better in all regards. With all the money of Mozilla they could've built a better, faster browser but they just didn't want to badly enough. And that's the tragedy.

That makes no sense. People might not know about WASM or Rust, but people like fast browsers. Rust is what powers Servo, which in turn made performance of Firefox somewhat acceptable. Gutting both teams is extremely short-sighted.

If you look today at who is studying an AP course for computer science in an American high school, what you will see is a group of people that are more male, white, urban, and more affluent than the country as a whole. That is what we need to address

As a male, white, urban, and affluent, perhaps he could demand to get replaced by a POC like some corporate board members have done, instead of endlessly yapping and proudly showing off his self-hating racism.

That document is not particularly enlightening either.

we're removing the types from internal code and making it pure JS. this reduces complexity and helps us ship a faster product

Yeah, because dropping static types from 10K lines of code is definitely not going to be a maintenance nightmare in the long run.

But perhaps this is something beyond the simpleton comprehension of us novice programmers

10K is a lot of code.

As a maintainer of a popular 3k LOC typescript library, even at 1k LOC you start running into frequent type-related bugs with JavaScript

Sadly, alacritty feels like such a waste of effort. The input lag is pretty bad, and text processing performance is a non-issue with most terminals. I've used xterm for years and never felt it was too slow at that.

Latency makes much more difference in how fast a terminal feels. This is where kitty does a fantastic job, even letting me trade some CPU cycles for really low latency with its options. I can strongly recommend it to anyone who values low latency.

The very first thing I do after buying any laptop is completely wiping everything and installing Linux or re-installing Windows.

I think it's best to always start from clean slate because even 'good' manufacturers put a tonne of shit in there. So in that sense, it doesn't really matter what the manufacturer does, apart from the terrible decision making that they should learn from.

I mean, buying a brand-new device and using Ubuntu 19.04 with the 5.0 kernel from a year ago and outdated packages is begging for trouble.

Since linux drivers live mostly in kernel space, for new devices I would imagine a lot of issues would be fixed by running the latest kernel or mainline for even newer hardware.

The next couple of years will be easy mode, for sure

Sadly this isn't true for a lot of math/computer science courses, speaking from very recent experience. While having an open book and even online access is an advantage, many profs implement measures ranging from webcam proctoring services to extremely difficult time-limited exams to compensate.