If they want Big Tech to pay, then write the law exactly Big Tech has to pay more in tax as they are so big and have the network effect etc. Don't write it complicated like this as it is hitting so many else that probably is not intended.
The problem with Rust is the compile time and build temp files. But that is not a problem once shipped. It is more about developers need to know more now
Why? Anything that ship should be precompiled like c code is today. If you want to compile everything yourself then move to Gentoo. If you need a programmering language then just install it. In my opinion now with AI able to write code in many languages, I see no need for Python anymore. Python is slow with high memory usage. I would rather see them replace Python with Go.
Yes, I dont know much about conpiler dependency.
Change => changing behavior etc. That is not a problem at all as long as it 100% compatible - which in this case is very hard to prove. The way to introduce change is therefore to say it is a new, different, standard. API version 2 or a new protocol, and let users migrate over to that by requesting the new version/protocol etc.
One difference is though that Ubuntu 26.10 is a new release(not LTS) so you would need to have a migration process anyway.
There are probably edge cases and you might not know about them until you actually run into them by running a script or similar but then it is to late as people dont want things to break. There is 30 years of testing, and expected behavior, behind on what we have today.
- I am on wired workstation computer - it does not have a battery
- Turning off power management in that tool help. Nice, now I can use it for real 😁 Maybe have menu "Dictation Service" -> Power Management On/Off would have helped me or something.
- When power management on and it were inactive, then when I pressed the hotkey button to talk or use the CLI --toggle, then I would expect it to actually start the service and show the splash counter and listen. Currently the user have to go to the menu and start the service manually if it has been idle. CLI show: "TuxTalk is loading its speech model. Recording starts as soon as it's ready." but I don't know when I can start to speak as I never see anything.
As far as showing the text as you speak, I tried that before and there’s a slight delay and I found that you’re trying to read it as you’re speaking and it just messes up your cadence because you’re still speaking as you’re reading what you just said. I’ll look into that again if people seem to really want that, but in practice I found it very distracting. Is there something else that you use where that works properly and you find it to be valuable?
-
Showing the text to me is just about knowing when to stop talking as it failed to recognized the correct language. I use the parakeet model that can't limit language. However, I don't know if I really need that feature, I will test more.
-
This is better than Handy for me as it does not cut the first letter in the output text and it does not consume 1 GB of RAM.
-
In snippets I have an idea to 'You say' and have an action to just run a command line program. Then I could have You say 'Open firefox in incognito mode' to run the command 'firefox -private-window'. But maybe that is better suited for other applications that have AI and try to be assistents.
Thank you! Request for improvement: show the text as I speak.
Edit: I notice on Fedora KDE Wayland that the Dictation Service just stops after a while of starting it. I need to manually start it again when I want to use it.
Best thing I heard all day is this 😁
Sad news. I hope they remove the latest update so no more users run into these problems.
Make it faster or actually better. When will the next successful product family launch like iPhone 2008?
Why kill anything to begin with? IMO better to error or slow down.