As far as we're concerned, yes. It literally would travel at the speed of light. But since the light from the momentarily-ago-normal universe would be traveling just ahead of it... Everything would look normal until it collapsed
- Posts
- 1
- Comments
- 53
- Joined
- 3 yr. ago
- Posts
- 1
- Comments
- 53
- Joined
- 3 yr. ago
- JumpDeleted
Permanently Deleted
That's a question no one has yet been able to answer definitively though both neuroscientists and philosophers are trying.
I'm of the opinion that "I" am a pattern, encoded in the physical interactions of my brain and body. I'm not certain if I have free will or just like to think I do. But I do believe that whatever makes me "me" is fully contained within the dimensions of my physical being.
I love this concept. A purely memetic threat. An idea that could destroy you merely by knowing it...
(If a specific set of improbabilities are true)
You cannot step into the same river twice - Heraclitus, ~550 BC
We are all a series of continuous evolution, alteration and change. "I" am not the same person who began this sentence. The idea that "I" cease to exist overnight and begin anew in the morning is meaningless. There is no one version of me. I live - and to live is to change!
Thank you for responding! I really liked this bit
with a (decently designed) UI, you merely have to remember the path you took to get to wherever you want to go, what buttons to press, what mouse movements to execute.
I think that's very insightful. I certainly have developed muscle-memory for many of my most-frequent commands in the CLI or editor of choice.
I agree about Visual Studio as a preference. I've used (or at least tried) dozens of IDE setups down the years from vi/emacs to JetBrains/VS to more esoteric things like Code Bubbles. I've found my personal happy place but I'd never tell someone else their way of working was wrong.
(Except for emacs devs. (Excepting again evil-mode emacs devs - who are merely confused and are approaching the light.)) ;)
I hope you take this in good humor and at least consider a TUI for your next project.
Absolutely. I see what you did there... 😉
But seriously, thank you for your response!
I think your comment about GUIs being better at displaying the current state and context was very insightful. Most CLI work I do is generally about composing a pipeline and shoving some sort of data through it. As a class of work, that's a common task, but certainly not the only thing I do with my PC.
Multistage operations like, say, Bluetooth pairing I definitely prefer to use the GUI for. I think it is partially because of the state tracking inherent in the process.
Thanks again!
As someone who genuinely loves the command line - I'd like to know more about your perspective. (Genuinely. I solemnly swear not to try to convince you of my perspective.)
What about GUIs appeals to you over a command line?
I like the CLI because it feels like a conversation with the computer. I explain what I want, combining commands as necessary, and the machine responds.
With GUIs I feel like I'm always relearning tools. Even something as straightforward as 'find and replace' has different keyboard shortcuts in most of the text-editing apps I use - and regex support is spotty.
Not to say that I think the terminal is best for all things. I do use an IDE and windowing environments. Just that - when there are CLI tools I tend to prefer them over an equivalent GUI tool.
Anyway, I'm interested to hear your perspective- what about GUIs works better for you? What about the CLI is failing you?
Thank you!
Lots of little quality of life things. For instance, in Kotlin types can be marked nullable or not. When you are passing a potential null into a non-nullable argument, the compiler raises an error.
But if you had already checked earlier in scope whether or not the value was null, the compiler remembers that the value is guaranteed not to be null and won't blow up.
Same for other typechecks. Once you have asserted that a value is a given type, you don't need to cast it everywhere else. The compiler will remember.
Let's start a patent troll company that exclusively deals in dark pattern bullshit. Then sue every company that implements any of our terrible patents for as much money as possible. Use the proceeds to
bribelobby congress to pass stronger consumer protection laws.Kotlin is Java with all the suck taken out.
It's a modern, ergonomic language that runs on the JVM and removes as much GD boilerplate as it can.
It's fantastic.
That one dude still using Delphi is getting screwed.
Also, these salary numbers seem... real low. I get that it's the median so maybe a huge number of overseas engineers are pulling the results down but in my neck of the woods 105K is less than what we pay juniors.
Argh. I hate that argument.
Yes - "Rewriting history" is a Bad Thing - but o argue that's only on 'main' (or other shared branches). You should (IMHO) absolutely rewrite your local history pre-push for exactly the reasons you state.
If you rewrite main's history and force your changes everybody else is gonna have conflicts. Also - history is important for certain debugging and investigation. Don't be that guy.
Before you push though... rebasing your work to be easily digestible and have a single(ish) focus per commit is so helpful.
- review is easier since concerns aren't mixed
- If a commit needs to be reverted it limits the collateral damage
- history is easier to follow because the commits tell a story
I use a stacked commit tool to help automate rebasing on upstream commits, but you can do it all with git pretty easily.
Anyway. Good on you; Keep the faith; etc etc. :)
Net removal of 1500 LoC...
I'm gonna make you break this up into multiple PRs before reviewing, but honestly, if your refactoring reduced the surface area by 20% I'm a happy man.
One of the best programmers I worked with was a hunt and peck typist.
His code was meticulous. I frequently learned things reading his PRs.
Pair programming with him otoh....
So... unlike Stable Diffusion or LLMs, the point of this research isn't actually to generate a direct analog to the input, in this case video games. It's testing to see if a generative model can encode the concepts of an interactive environment.
Games in general have long been used in AI research because they are models of some aspect of reality. In this case, the researchers want to see if a generative AI can learn to predict the environment just by watching things happen. You know, like real brains do.
E.g. can we train something that learns the rules of reality just by watching video combined with "input signals". If so, it opens up whole new methods for training robots to interact with the real world.
That's why this is newsworthy beyond just "AI Buzz" cycle.
- JumpDeleted
Permanently Deleted
To be horribly pedantic... Not necessarily!
It could be Apple users -> Windows users -> Linux users -- with larger numbers of Apple -> Windows conversions than Windows -> Linux conversions...
You know.
Maybe.
Nah. AI-generated content doesn't "ruin" the internet any more than Disney can "ruin" Star Wars.
The good stuff is still there. Always has been. Low effort Sora vids don't reduce the entertainment value of - say - Tom Scott's oeuvre.
What AI spam does its the same thing all spam has ever done - increases the amount of noise we have to filter.
Noise is always cheaper to manufacture than signal so it always appears to dominate. ... but any given noise has no lasting commercial value, while high quality signal always does. That's why the old newspaper companies are still around even when you can just read Twitter to get the gist of world events.
Intelligence and thoughtful design matter.
We're gonna see a lot of AI spam for a couple years. But I promise you someone is already working hard to figure out how to identify it.
When I first joined the internet it was considered virtually impossible to detect and block spam reliably. Now, email spam is a rare annoyance that only impacts us occasionally.
Someone will crack AI-detection, or better yet, solve "this is noise" detection once and for all.
In order to add their names to your dictionary. You don't have to allow it. But given that there's no internet access for the keyboard - it seems pretty safe