Hacker News new | past | comments | ask | show | jobs | submit | FFFXXX's comments login

The 95% safe Rust Code does not use any auto-vectorization (https://cliffle.com/p/dangerust/5/nbody-5.rs)

Only the 100% Rust-safe implementation uses auto-vectorization and is at 0.73% of the RUNTIME of the C code. (https://cliffle.com/p/dangerust/6/#performance-evaluation)


*73%

No, the Rust code is at 97% of the RUNTIME of the C code (https://cliffle.com/p/dangerust/5/#evaluation) when keeping the manual vectorization.

One interesting usecase is that you can run a tauri app without any webview windows just as a system tray icon and only spawn a webview window when necessary.

This kind of makes it way more lightweight but only in some situations (obv. heavily depending on the functionality of the app).


Would this be for a service style app that happens to have a UI when you need to configure it? If so that's an... interesting idea, but considering the UI is less important I'd probably mind it less (as someone who is not a fan of Electron apps).


I built a syncing tool that needed to run in the background with a simple UI to control it.

I used tauri so I could easily make that cross-platform toolbar app.

Some menu items spawn a webview (things like settings), everything else is in Rust.


Thats awesome, now I'm going to have to find a reason to use this for something ;)

Tiny nitpick: the #![allow()] generates a 'warning: unused attribute' warning for me.

If you change it to #![allow(unused_attributes)] it disables the warning for itself.


Nice catch! That warning definitely wasn't emitted the last time I tried this.. I don't know about using something like your suggestion which has actual side effects, but probably something like #![cfg_attr(invalid, allow(unused_attributes))] instead would work (without side effects).


It possible to disable this plugin. I have it disabled.[1]

The linked YouTrack thread[2] in the article says so as well. It is just not possible to remove the plugin entirely from your device.

Regarding the plugin being enabled by default the official response by Jetbrains says [3]

  The AI Assistant plugin is enabled by default and menu items and tool windows are visible in the UI. However, AI Assistant functionality is NOT available by default, and NO requests are sent to the JetBrains AI Service unless ALL of the following conditions are met:
  
  - The user has explicitly consented to use the AI Assistant and is using the trial or has purchased the corresponding subscription.
  - The AI Assistant has not been disabled for a particular project.
  - In the case of a commercial IDE license, the AI Assistant has to have been enabled at the organizational level. We’d like to reiterate that for commercial IDE licenses, unless this is explicitly enabled by your organization’s administrators, AI Assistant will not be available.
I'm not saying this is perfect and this can obviously still be a problem on e.g work devices.

[1] https://imgur.com/ETyFlCZ

[2] https://youtrack.jetbrains.com/issue/LLM-1760/Can-not-remove...

[3] https://youtrack.jetbrains.com/issue/LLM-1760/Can-not-remove...


On release, IIRC, disabling it did not work persistently, ostensibly due to a combination of bugs, so a lot of people found that especially egregious.

I think it was something like it would default to enabled again if you uninstalled the updated version, since you can't uninstall the bundled version? I don't quite recall.

But that made people very upset indeed.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: