Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Rendering time? (Score 1) 17

"whose rendering time is long if the target pixel is non-white and short if it is white"

Huh? There's nothing special about white in the colour gamut, why would it be quicker to render?

Aside from that I don't quite follow how the attack works. Does it try and render pixels in its own window then these somehow slow down depending on the pixels beneath in a masked window? This is all done in the GPU surely, not software?

Comment Re:Wtf? (Score 1) 74

"Yes and not because "they are done","

They are done. "ls" for example doesn't need to do anything new.

"Or may be because C++ isn't fun to work with "

Oh I'm sorry, I didn't realise the appropriate language choice was one that was "fun". I thought we were talking about adults here, not preschoolers.

"C++ has no traits"

Wrong.

"no thread safety"

Wrong.

" no built-in utf-8 strings"

Plenty of libraries do it.

"no proper macros"

Define proper macro. C had them, C++ has them + constexpr which you've probably never heard of because you clearly know squat about modern C++ and are using something you heard about C++ in the 90s to form your opinion.

"no immutability by default"

Wrong. FFS what do you think the "const" and "mutable" keywords are for??

" it is still inherently unsafe even without using the raw pointer"

Vague handwaving crap demonstrating you have no clue.

"Why not, it will be an interesting project and I can only welcome it"

Err , maybe because python isn't shipped by default in a lot of distros so writing your utils in it might not be the best idea. Also in long pipe chains kicking off an entire python interpreter for each command would be hideously inefficient.

But then I wouldn't expect you to understand, you're just a clueless kid who is going to have an encounter with IT reality one day that will come as a shock to you.

Comment Re:Wtf? (Score 4, Insightful) 74

"And it's not only about the existing code but also adding a new code."

I doubt many command line utils will be updated anytime soon. Most of them have been a done deal for years.

"Rust is a modern language with a lot of features missing in C"

So is C++ and there are far more C++ devs than rust devs and they could have been rewritten in C++ years ago but sensible people realised that if it ain't broke don't fix it.

"ust naming a few like traits, generics, utf-8 strings, FP-style constructs, immutability, standard library, thread safety, async"

Wow, cutting edge! See C++.

"is much more attractive for the new developers."

So is Python, perhaps they should be rewritten in that if popularity is a reason.

Comment Re:Wtf? (Score 4, Insightful) 74

"It's not about memory leaks but memory safety"

Are there many safety issues in these utilities? I presume they've done code analysis and found loads then?

"and much better maintainability that legacy GNU C code"

BS. There's nothing special about Rust wrt maintanability plus there's a FAR greater pool of C devs than Rust devs who can check any new code.

Oh, and just because code is old, debugged and works doesn't make it "legacy". No serious devs are interested in the Shiny New Thing unless it does something incredibly special and useful. I'm not seeing that here.

Comment Re:AppArmor or SELinux (Score 2) 74

I'm all for pointing out the foibles of windows, but I'm afraid security and firewall rules are standard in the corporate world and have been for decades. If you think any of the corporate *nixes like Solaris of HP-UX didn't have any of this then you really need to get yourself up to speed as to how IT works in a business.

Comment Wtf? (Score 5, Interesting) 74

"the Rust replacements for standard gnu utilities were busted."

I had to google this - I didn't realise people were wasting time and effort in a pointless re-write of utilities that have probably been debugged better than any other code out there!

Do these Rust zealots not understand that memory leaks are only one of many potential bugs and in a fire and forget utility that may only run for literally microseconds they're borderline irrelevant compared to logic errors? And if you rewrite complicated code in another language you're going to make those sorts of mistakes.

Comment Re:Early days? Seriously? (Score 1) 16

"As soon as a prototype is ready IT MUST GO LIVE within 4 to 6 month"

BS. It takes far longer than that to write a half decent game for any platform these days. Its not the 1990s any more. So sure , they could release it in 4-6 months so long as the customers didn't mind having any software for it except emulated PS5 titles.

Comment Re: Realistic engine sounds... (Score 1) 130

Shhhh, don't talk reality around here, the EV club don't like it, they think everyone is happy sitting around for 30 mins to charge up - assuming they can even find a feckin charger and its working - just so they have the supposed kudos of owning in EV.

Most people just want a vehicle that gets them from A to B as con veniently as possible, not a posing pouch or political statement.

Comment Realistic engine sounds... (Score 1) 130

... are entirely possible. Sampler synthesizers have been available since the late 1970s and even the cheapest onboard PC sound chip has been able to do it for 20 years so there is zero not to have realistic engine sounds in 2025. Quite clearly they deliberately use unrealistic sounds - for what reason I have absolutely no idea.

Slashdot Top Deals

OS/2 must die!

Working...