akira2501

> Embedding images into the page was a killer feature for HTML

I'd disagree slightly. Users did not have the high bandwidth always on connections then that they do now. Images were nice but were also avoided as they made pages "slow". The main reason lightboxes and other clickable thumbnails came into existence.

> was still doggedly text based because they were still supporting the VT100 users

I used lynx and links for a very long time. What made me switch was the prevalence and ultimate utility of JavaScript. It turned simple pages that were best consumed after being fully downloaded into complete progressive applications.

It's possible they're just naive.

> The audience might not notice, and could (IMHO) easily be duped into supporting good causes!

What a deranged fantasy this is and yet how often it shows up. The audience will notice. Those who don't and eventually discover your duplicity will never forgive you for it. What you propose is disgusting and amoral, as it has no value, and is designed to mollify yourself by bulling people you clearly perceive as being beneath you.

This is ridiculous clap trap. Why did you submit this here?

Using print server vulnerabilities to gain local privilege escalation is reminiscent of Windows 95. The year of "Linux on the Desktop," I guess.

> I've been putting off digging into AWS for years now

In my opinion people end up in these billing situations because they don't actually "dig in" to AWS. They make their pricing easily accessible, and while it's not always easy to understand, it is relatively easy to test as most costs scale nearly linearly.

> the rational fear of waking up to massive charges.

Stay away from the "wrapper" services. AWS Amplify, or Cloudformation, or any of their Stack type offerings. Use the core services directly yourself. All services have an API. Getting an API key tied to an IAM user is as simple as clicking a button.

Everything else is manageable with reasonable caching and ensuring that your cost model is matched to your revenue model so the services that auto scale cost a nearly fixed percentage of your revenue regardless of current demand. We take seasonal loads without even noticing most years.

Bandwidth is the only real nightmare on AWS, but they offer automatic long term discounts through the console, and slightly better contract discounts through a sales rep. Avoid EC2 for this reason and because internal bandwidth is more expensive from EC2 and favor direct use of Lambda + S3 + CloudFront.

After about 3 months it became pretty easy to predict what combination of services would be the most cost effective to use in the implementation of new user facing functionality.

And how do you account for the fact it has no predictive power? Following the logic of your assertion we see very few cases which actually reach it. Wouldn't that suggest it is incorrect or at least incomplete in some way?

They used to be.

    $ cat /proc/sys/fs/file-max
    3235242

And `nr_open` has been 1048576 for a long time. The default quota limit is 1024 but that is easy to change.

They build this work force in the office. People went through their probationary period in the office. They were moved home out of concern for health.

While you may be able to do this, I'm not sure it's so easy to sustain it, or to replace the hiring model with a fully "hire into WFH" mode.

Running a company is a lot more than putting a time clock on the wall.

> maybe they know something about being a super successful company?

If being successful is simply a matter of knowing a few things then why aren't more businesses successful? Why wouldn't those employees in the know just leave and start their own business?

> I would prefer extending poll to support things other than file descriptors, instead of converting everything a file descriptor to be able to use poll.

Why? The ability to block on these descriptors as a one off rather than wrapping into a poll makes them extremely useful and avoids the race issues that exist with signal handlers and other non-blocking mechanisms.

signalfd, timerfd, eventfd, userfaultfd, pidfd are all great applications of this strategy.

> In another exercise, teens were asked to identify which of two pieces of content about Coca-Cola’s plastic waste was more credible: a press release from Coca-Cola or an article from Reuters. The results were too close for comfort for the report, with only 56% of teens choosing the Reuters article as more trustworthy.

So, at the end of the day, you're concerned over which article they're choosing to uncritically put their faith in? If this is the case then I'm not sure `news literacy` is worth anything.

I think you'd want "information literacy." The ability to find studies and understand them, to ask questions about them, and to do their own follow up work based off of them.

If all you're doing is asking them to choose between two articles then their world view is entirely controlled by publishers, and we've reduced them down to deciding which publisher is more credible, and given them no tools to ask important questions on their own. I can't think of anything less valuable for an education system to involve itself in.

> `if let` is more or less syntax sugar for `match`.

Which are new features for systems languages that otherwise rely on RAII for locking. So it's in the class of "original sin."

> so we are pretty much stuck with it.

You could refuse to compile it under some set of flags. Isn't that the basic value premise of the language here?

I see it as a consequence of Rust being too liberal with additions to the language. It's hard to maintain some of these guarantees in the presence of certain syntactic forms. This happens in all languages.

It is a little hilarious to see a rustaceon write:

> and you can sus out if a program is going to cause a deadlock by just making sure you aren't acquiring multiple simultaneous locks.

Ah.. not a problem! You just have to not ever have the problem. Then, of course at the opposite end of the article:

> I wrote this block because this has specifically bitten different Rust crates in the wasmCloud project multiple times

:D

> I find that I like English "sentence case" for it,

I could go either way, but if you want to go back and modify a query, this makes it more difficult for me. I just use a block syntax for my queries:

    SELECT   *
    FROM     the_table
    WHERE    some_column = 12
    AND      other_column IS NOT NULL
    ORDER BY order_column;

> it's not exactly a burden to lift it a little.

Human dexterity is not constant. Some people have injuries which compromise them.

> And there are highly practical workarounds:

Apple. A consumer product company where every _single_ product has some massive defect which must be apologized around.

Which is fine.. but I'm not sure how that justifies their typical price point.

> Burnout is a work life balance thing

It's more than that. Perhaps you haven't been in a position to accept a lot of resignations in your career. Burnout is most definitely implicated by the work place itself, specific work assignments, and general office culture.

> don't have a near infinity list, then that means you don't have a roadmap

Are you talking only about startups? That would make sense. In the more general case I doubt your assertion here. Does this fragment truly sound rational to you on a second reading?

> and this can always be done in the context of the work.

The very article this thread is attached to clearly shows how false this is.

> Then why didn't Java do better?

Bad UI frameworks that failed to be usable and/or compatible across systems. Cross compiling is more than producing foreign executables.

The F35 does not have a dedicated radio control panel. It's a menu driven operation through a multi function display. More damningly these electrical overload failures are known on the platform.

The plane is just a poorly designed death trap.

> we're stuck picking up the slack

You may be on a team that has decided "developer burnout" is just an inevitable and acceptable cost of business.

> since there's a near infinity backlog?

Which is a problem in and of itself. In any case I'm only going to be able to give you like 4, real, solid hours of work a day on that log. The other 4 will be team coordination, managing that log, and stress management maybe while I hate eat my lunch.

> everyone is given exploration time

Call it "skill investment time." We're in a fast moving industry and keeping heads down for too long is destructive personally and organizationally. It's also the pathway to getting more than the basic level of engagement above.

I wonder if that's why Angela Collier posted this recently:

https://www.youtube.com/watch?v=zatpZgVWf8w&t=1191s

The web took off because cross compiling sucks.

Change my mind.

Classic bullying.

We know now that while these laws have local impacts they clearly also have global impacts and they are not always positive.

Attempting to use the local success of the EPA Clean Air Act to justify a flat 16%+ increase in the price of a widely used and important commodity is inappropriate.

Not all roads are created equally or have equal weight ratings. I'm sure you've seen signs depicting restrictions on certain roads. These smaller roads tend to be owned and maintained by smaller municipalities who are less able to afford upgrades or maintenance.

In any case, point still stands, you're more than "one smart decision" away from having electrified the American fleet of vehicles.

> “An EPA analysis showed that the Clean Air Act’s benefits outweigh its costs by a factor of 30.”

For Americans. For the Chinese? Probably a different story.

You're going to need an actual maintenance infrastructure which is currently lacking. You're also going to need to improve the roads themselves due to the additional weight of the vehicles. You need a massive rollout of charging stations.

If it were only the lack of nuclear plants.

You can't just wave your hands about the climate and then hope to create a new market overnight.

In C's grammar you would need to wrap the {} as ({}) in order to get into a block expression scope from an argument list.

Every President and Member of Congress for the past 20 years has failed on this account. I think a different lens to view this through would be more useful.

> They require a bar that is impossible to prove in real life.

Hardly. Discovery is an amazingly powerful tool. The problem seems to be most of these cases are argued in front of bench trials and not jury trials. Judges are often swayed by technocratic arguments and can be easily convinced to ignore the impact of monopolies on labor markets in favor of the simple consumer pricing argument.

> and allow a lot more power to split up and fine large companies

We already have that power. You might ask why the DOJ has refused to use it in the past two decades.

It used to be a lot easier to get a law degree. California is currently the only state that will let you sit for the bar without a JD. You have to have equivalent work experience but you can still as a completely private citizen get yourself into practice.

Industrial gatekeeping is a real problem. One of the indirect mechanisms is the accumulated complexity of the law and the seeming inability for legislatures to remove outdated and fruitless laws from their books. Unsurprisingly the people most capable of achieving this are not interested in doing it.