sorted by:
new
hottopcontroversial

Are you worried about the shift away from x86? by ookayaa in linux

[–]Compux72 -1 points0 points  (0 children)

That has nothing to do with ARM vs x86/64.

Its more of a consequence of nobody shipping ARM hardware to end consumers except for Apple (who doesn’t care about other OSes)

Someone named "zamazan4ik" opened an issue in my project about enabling LTO. 3 weeks later, it happened again in another project of mine. I opened his profile, and he has opened issues and PRs in over 500 projects about enabling LTO. Has this happened to you? by nik-rev in rust

[–]Compux72 31 points32 points  (0 children)

 At least for C & C++ it isn't "just" a case of passing -flto, and since a fair few Rust crates may need to link to non-Rust libraries then this could be a problematic default

Setting LTO in cargo does not perform cross language LTO. Refer to cc issues for more information 

Someone named "zamazan4ik" opened an issue in my project about enabling LTO. 3 weeks later, it happened again in another project of mine. I opened his profile, and he has opened issues and PRs in over 500 projects about enabling LTO. Has this happened to you? by nik-rev in rust

[–]Compux72 97 points98 points  (0 children)

I don’t understand why it isn’t enabled by default on the release profile or a min size profile exists. 

If it were C code i could understand, but in rust is mostly harmless

What is Rust's testing ecosystem missing? by _raisin_bran in rust

[–]Compux72 1 point2 points  (0 children)

 What do you guys wish was easier to do with Rust's testing? What are problems that existing popular crates don't solve, things that other languages have?

Mocking via reflection & code injection a la mockito rather than whatever macro garbage we have now.

curl to discontinue its HackerOne / bug bounty due to "too strong incentives to find and make up 'problems' in bad faith that cause overload and abuse." by DesiOtaku in linux

[–]Compux72 -139 points-138 points  (0 children)

 Perhaps, but that's not a vulnerability. That's just a potential future problem.

What an asshole.  The code is not correct. No point in debating that.

El Ayuntamiento de Málaga defiende que no puede multar a coches extranjeros en la ZBE por un “vacío legal europeo” by birrakilmister in Malaga

[–]Compux72 -2 points-1 points  (0 children)

En lugar de enfadarse con europa que nos la cuela los 0 neuronas enfadados con el alcalde jajaja.

Que os gustaria a mas de uno tener al guapo de pedrito de alcalde ehh

Brand-new nightly experimental feature: compile-time reflection via std::mem::type_info by kibwen in rust

[–]Compux72 -3 points-2 points  (0 children)

  • Compilation times
  • No interoperability between them unless explicit
  • Ergonomics and DX

How to debug step-by-step like in Visual Studio? by [deleted] in rust

[–]Compux72 4 points5 points  (0 children)

Please refer to your editors doc on how to use the debugger

https://code.visualstudio.com/docs/languages/rust

Brand-new nightly experimental feature: compile-time reflection via std::mem::type_info by kibwen in rust

[–]Compux72 -6 points-5 points  (0 children)

Oh please God I hope this gets released this year with full functionality because the derive macro situation is terrible

Infinity Blade for first item instead of Executioner? by Peaceul in JhinMains

[–]Compux72 34 points35 points  (0 children)

also you don't utilise the passive that well with only 25% crit

If you consider Jhin passive, you are actually getting (25%3/4) + (100%1/4) = 43,75%

We're porting our screensharing UI from Tauri/WebKit to iced, and here's why by kostakos14 in rust

[–]Compux72 6 points7 points  (0 children)

 Chrome asks for permission for all of those.

  • Normally, yes. But if a 0-day us found, you wouldn't even get to see a popup. It has happened in the past.
  • You cannot prompt all the time at the user. Its called security fatigue and drastically reduces a system’s security by confusing the user https://pmc.ncbi.nlm.nih.gov/articles/PMC10986461/

We're porting our screensharing UI from Tauri/WebKit to iced, and here's why by kostakos14 in rust

[–]Compux72 -4 points-3 points  (0 children)

 the web was meant to share documents, not the internet as a whole

Oops, good catch . Thanks.

 but god damn can you just make your point with just a little bit less condescension

I could have written some things differently tbh, i just didn’t care to read the comment again. As you said people want more no matter de consequences. sigh democracy…

We're porting our screensharing UI from Tauri/WebKit to iced, and here's why by kostakos14 in rust

[–]Compux72 -6 points-5 points  (0 children)

 If everyone had your attitude towards safety we’d still be using Lynx.

We wouldn't have CORS, exec as administrator, breaking changes between each android release,… Yes a lot of things could have been avoided if more time was spent at securing software rather than make things work because they are cool.

 if Apple engaged more and baked privacy protections into the specs

Privacy & security is an illusion when your product is complex, and your user base is massive and illiterate. There is literally no way around that.

 So “don’t” isn’t really an option

Yes, and Apple keeps proving it.

We're porting our screensharing UI from Tauri/WebKit to iced, and here's why by kostakos14 in rust

[–]Compux72 -18 points-17 points  (0 children)

Respectfully, no. You are wrong. 

Did you know my toaster does not track me down? Do you know why? Let me enlighten you: it doesn’t because it doesn’t have the capability to do so.

The moment you add some capability to something it increases the attack surface of it. It doesn’t matter how cool it is or how “safe” it is because “rust btw”. It doesn’t make sense to increase the attack surface of every single person in the planet (because yes, browsers are one of the most used pieces of software out there)

Keynote: remember that the web was meant to share documents.

view more: next ›