optymizer
I for one prefer taking pictures with the Meta glasses when traveling. Taking a phone out of your pocket, launching an app, holding the phone in front of you until you align the object in focus and then tapping a button starts feeling so inelegant after a while, compared to a quick press on the side of the glasses. The picture also comes out looking exactly how you saw it, videos are from your POV.
When driving, I like hearing the GPS navigation instructions discreetly without having my ears blocked by earphones and the car music being interrupted (also my wife can't stand the navigation voice and always asks me to silence it. With the glasses I can still hear the instructions).
Again, when traveling, if I'm staring at a building or something I'm curious about, I can ask the AI to tell me more things about the thing I'm looking at. It's quick and convenient.
(not affiliated, I did a simple search before writing an app myself)
I'll have to explain it to the wife: "well, you see, we cant live in this house anymore because AI in Notepad was just too much".
I'll dial up my ethical and moral stance on software up to 11 when I see a proper social safety net in this country, with free healthcare and free education.
And if we cant all agree on having even those vital things for free, then relying on collective agreement on software issues will never work in practice so my sacrifice would be for nothing. I would just end up being the dumb idealist.
There is always someone who will take advantage of the prisoners dilemma.
You were never able to "click a link" in Notepad in the past.
Mixing responsibilities brings with it lots of baggage, security vulnerabilities being one of them.
Because the society in US is arranged as a competition with no safety net and where your employer has a disproportionate amount of influence on your well being and the happiness of your kids.
I'm not going to give up $1M in total comp and excellent insurance for my family because you and I don't like where AI is going.
And if you're wrong, and shit hits the fan for whatever reason, who's going to fix that? You? No, he's going to have to fix that, because nobody else is going to step in.
It's easy to tell others that it's going to be OK, but put your money where your mouth is. Put $1M in a fund that he can access should he no longer be able to find employment. Then he'll have absolute certainty that it's going to be OK.
Something tells me you're not going to do that. Something tells me that what you would do if shit hits the fan, is you're going to tell him that he should find solace in the fact that while he's working for 1/5th of his former total comp, putting in more hours at the same time, seeing his kids less, not putting his kids through private school to give them the best chance at the best education, that, at least, some kid out there isn't watching 6-7 videos on the tablet that their parents use to do less parenting.
I'll note a few things:
1. 'fast' without benchmarks is just marketing speak. I keep seing "fast", "super fast" on the GitHub page but nothing to substantiate the claims. How fast is it compared to using D, or even C?
2. 'Download glang' link is broken
3. Why would I use G and not D directly? D generates small binaries as well.
4. What does the 'std' library include? You're mentioning 'println' and 'newline', while people expect data structures and components they can reuse. Is the D standard library accessible?
5. I couldn't find a documentation page easily, but I see you plan on overhauling the documentation
6. Including a package manager is awesome.
7. Do you have any interop with C, D or Java?
A few observations related to naming:
8. G Language is already used by a few pieces of software, though nothing too widely known (https://en.wikipedia.org/wiki/G_programming_language).
9. If I thought my language is worthy of a single letter name, I'd swing for the fences and name the compiler executable 'g', not 'glang'. You're already using the .g file extension for G Lang source code, so might as well go big with the command too.
10. Speaking of glang, it's super close to golang by Google
11. Your Fuchsia shell's name conflicts with the Fuchsia OS (fuchsia.dev) by Google
I'm not a big fan of the syntax, but I wish you good luck. I hope to keep hearing about your language in the future.
After using AI to code, I came to the same conclusion myself. Interns and juniors are fully cooked:
- Companies will replace them with AI, telling seniors to use AI instead of juniors
- As a junior, AI is a click away, so why would you spend sleepless nights painstakingly acquiring those fundamentals?
Their only hope is to use AI to accelerate their own _learning_, not their performance. Performance will come after the learning phase.
If you're young, use AI as a personal TA, don't use it to write the code for you.
Of the intermediate features, I use tabs and, more recently, split windows.
My favorite 'advanced' feature is visual block selection and replacement over multiple lines - super convenient.
I would however download a new browser that promises to not have all these bad features and has stripped them straight from the source code. For example, I switched from Chrome to Brave because it blocks ads.
From Wikipedia: "End-to-end encryption (E2EE) is a method of implementing a secure communication system where only the sender and intended recipient can read the messages."
Both ends do not need to be under your control for E2EE.
I understand they're trying to go for a whimsical and fun feeling, but imo as implemented it is far from "really well made".
* Blood, Sweat and Pixels
* Press Reset
* Play Nice
* Masters of Doom
* Color & Light
* Video Game Art
* 2d Graphics Programming for Games (in progress)
A few years ago I was the TL on a FAANG Android project, where for a few months I was doing more spreadsheet/TPM work than usual, and didn't have much time for coding. Once we had a meeting where I ended up coding in Kotlin live in front of a dozen younger devs to discuss the implementation of some feature. My work background is Android and Java/Kotlin, but at the time I was mostly coding in C on the side, and in the moment my brain just forgot what the syntax in Kotlin is for a "switch-case" statement, so I wrote "switch", "match", etc, struggling like a first year student, while everyone watched me fumble, until I just gave up and said: "oh my god, I'm forgetting Kotlin. What the hell is the switch keyword in Kotlin called?". Then someone said: "it's when".
I felt old and a little embarrassed, but mostly I was surprised at how quickly I could forget a programming language I used daily.
The author had a shower thought. It was poorly explored, poorly argued and deliberately packaged in complex language to hide the lack of substance. The bibtex reference at the end is the cherry on top.
10/10 should be required reading for all humans
My uncle had a Lada 2101 ("Kopeyka", i.e. "1 cent") and that was a rust bucket, but he also drove it on unpaved country hills for decades. He was growing watermelons and he used his Lada to transport the watermelons to the farmer's market. You would be amazed to see how many watermelons fit in that small car.
Both of these were better than my grandfather's Moskvich. I actually liked the rugged feel of the Moskvich, but it had a known design fault with the handbrake causing it to malfunction, so for uphill parking purposes, we always had to carry a brick or two in the trunk.
This is the downside of not owning both software and hardware. The integration is lacking. I already gave money to Lenovo when I bought my laptop, and clearly they're not going to support Ubuntu. Maybe if I gave money to Ubuntu, they would support this hardware. It's worth a try, because leaving it at "sucks" is not acceptable.
Only because individuals would presumably open LLCs
> But when there is money in it, the work tends to focus on quarterly revenue.
I don't think the choice is between "John works on this project 11pm - 1am on the days he feels like it" and "John wants to IPO his company". I'm advocating for "John works on this project 3 days of the week because people pay him a small fee for using his project".
> Surely the money you gave to Lenovo would cover that?
The money I gave to Lenovo went to Microsoft for an OEM license to the pre-installed Windows OS. When I download Ubuntu and install that on my laptop, Lenovo couldn't be bothered to see if closing the lid suspends the laptop or not.
Should Lenovo write drivers for my custom kernel as well? As a business, why should Lenovo bother to implement resume capabilities for an OS that is a rounding error for their consumer line of laptops?
Sure, there is great value in having a free (in both senses) operating system, but at the same time the year of Linux desktop is a running joke.
To be blunt, money motivates people to do the work they otherwise would not do. It's soul crushing to run the 400th manual test. It's not sexy to work on a lot of the bugs that affect real users, so, when there's no money in it, the work tends to focus in areas of passion and feature development.
Maybe if we all sent $1 to open source projects we use, there'd be enough funding to hire QA people and engineers to fix things like Ubuntu's suspend/resume on my Lenovo laptop, you know?
Our experiences do not match. I used Borland Delphi to build business apps 20 years ago just using the UI builder. I've been using Android Studio to build apps at FAANGs for 10 years now and I cannot remember the last time the Design tab was useful - it was always faster and more reliable to just edit the XML file.
Yes, Delphi didn't do resizing windows and crashed half the time, but I was pretty happy with the WYSIWYG / UI building functionality for production apps.
Android Studio's UI builder is nowhere near that level of usefulness. I have a hard time believing anyone is using the UI builder in Android Studio for anything other than tutorials or entry level Android apps. It doesn't render the layout properly 90% of the time, or just renders some placeholders with no content and calls it a day.
For a modern IDE, Android Studio is somewhere between just OK and bad, mostly because it has features the other IDEs didn't at the time, but the dev experience is behind Turbo Pascal in the 90s on MS DOS. The editor is laggy. The debugger is slow and hangs often. The list goes on, but I'll stop the rant here.