Microsoft doing Microsoft things, even with all those fresh coats of "open source" paint they bathe themselves in the last decade they really can't change their DNA.
Expect the amount of f*ckery to increase as the AI realities set in but the number has to go up either way.
It reminds me of the good old days of Visual Studio + .NET + SQL Server where they played these games too.
"Just" some Copilot integration (in the form of chat or smart suggestions) is just the start.
The next major Windows 11 update coming in 2026 will have full agentic AI with full control over your (your?) PC. And it will hard require a pretty recent processor with Neural Processor Unit to make it work (so a lot more e-waste is coming).
Nope, you go to upgrade, because windows update downloaded it and restarted, and it tells you “Your processor is not supported”.
Why would it be any different than the Windows 7 -> Windows 10 debacle? Disabling entire processor families after it boots into installation and wiped the previous windows.
I think they fixed that to some degree. I have an old win10 PC that now has a persistent "upgrade to W11" banner that informs me my PC is below spec, so I can't upgrade. Fine by me!
A 2025 Linux kernel with all recent features is able to boot on a system from 2006.
Likewise the Windows 11 (which is just a rebranded Windows 10, just look at the full build number which should start with 10.x) kernel could boot systems from ~2017 onwards. Maybe with some kernel features disabled which most (if not all) Windows 10 users would not miss anyway, but it could still boot without any issues. Those running a Rufus-patched Windows 11 are living proof of this.
This never was a technical issue, or one which could cost them money, but a cold blooded business decision which generated thousands upon thousands of kilos of e-waste.
>A 2025 Linux kernel with all recent features is able to boot on a system from 2006.
Because no one on the kernel team likes deleting code, specifically because someone will try to install it on their old ass work laptop from a decade ago.
Microsoft choosing not to support that old ass laptop is a company choice. There are costs involved with maintaining the support structure. Whereas Linux is primarily funded by enterprises who use it on servers, which may not be updated hardware wise in a longer period of time.
If Linus Torvalds or Miguel De Icaza introduce copilot, I swear I’m going to go all in on BSD.
Almost nobody has this functionality on their desktop processor. I hate Microsoft as much as the next guy but there's enough real problems to yell about without making some up. The agentic AI will even be entirely opt in.
It's not. Like TPM and several new CPU features are a hard requirement for Windows 11, which are patched out by tools like Rufus but can lead to a broken system with every single update you install, a NPU is a hard requirement for the upcoming major update with agentic AI.
They got a storm of criticism after that announcement, but Microsoft seemingly has not given a single fuck about that and has not backtracked on this decision.
(Just like they technically could have allowed Windows 11 to run on older PCs with some disabled features out of the box, but didn't)
Fuck did it really? How on earth does that pan out? Who uses notepad? Writers? Word. Coders? Vim or VSCode or <IDE of choice>. I just don’t understand their logic.
They make this beautiful pasture (Windows XP wallpaper) and then lay mines all over the field. Put up signs that say “Free Lemonade” and charge for parking.
It still starts very fast, even with quite large files and line wrapping. (pretty much on par with lite-xl, though lite-xl did get much faster with some recent version. prior to it though, it was easier and faster to launch notepad)
I've heard Github makes more money from copilot than everything else combined. You can think what you want about the strategy, but it's hard to ignore that.
But enterprises may negotiate not to use (and pay) Copilot, can't they? Or go with another provider if it's such a big deal. Plus it being enabled by default in every VS Code (I haven't checked this, last I remember you need to sign in with GitHub) gets you on the free tier where you make zero revenue for Microsoft and some expense (not too much, probably).
I’m not sure why people are surprised. If you watch Nadella interviews, he tells you what he thinks and where he wants to take the company.
He touts AI, services, agentic copilot, and all the other stuff customers are railing against.
Some Windows manager got crucified on X recently for an enthusiastic tweet about turning Windows into an agentic OS. People called for this persons firing. But, this was straight out of Nadella’s playbook.
Windows users are not customers. Businesses are. Tech conglomerates and everyone adjacent are going for the big money, it's what everyone is doing , it really is a fantastic world devoid of anything but ROI numbers. The fastest way to get rich or die trying, gangstas got nothing on these cats.
I'm doubtful many businesses are requesting many of these features.
I don't think it's wise for them to want stuff like Recall (data exfiltration) or current state of the art agents doing calculations or analysis for them -- at least without a qualified human closely reviewing it's output and conclusions.
I do see businesses wanting simpler, more reliable software with fluid and consistent interfaces, but MSFT isn't focusing on that.
Business owners are stupid, and they, too, need to signal to their investors that they're "all in" on AI.
AI is, currently, more of a culture than a product for businesses. At least, the ones that don't literally make the models. I'm sure a lot of business owners really do want all the AI stuff, and then their employees will just work around it, like they do with all sales or signaling driven decisions.
The bit that really annoyed me: you can't even remove the Copilot button from the Office ribbon any more. Microsoft simply have hidden the option in the Ribbon customisation settings.
Even though I don't use it, and have disabled as much Copilot functionality as Microsoft will let me.
At least in my experience, most of the poor UX can be explained by the fact that LG shipped underpowered hardware for the OS and apps that are expected to run on it. I bought my TV a year ago and it lags or loses input on the main menu, and it's even worse in apps. Forget it if you want to use the overlay menu to change a setting lol
If you remember Palm/HP webOS, it had Preware homebrew that didn't require exploits to run, it was supported by default and was amazing. LG patched the one vuln that would have let me at least root the TV.
The Android TV devices I bought from reputable retailers are at least beefy enough to handle input without lag, and I can run whatever APK I want on them.
The only software that I want to run on my TV are TV channels, and all the streaming operators, for anything else I have devices that I don't need to root.
My Android TV on the other room is equally just good enough to run Android, also not going to win any benchmarks.
Agree that the overlay menus on WebOS take their time to come up, but I am not going into them all the time for them to get into my nerves.
I have a C8 from LG, and I'm so happy with it after so many years, works wonderfully as a dumb panel, and a great panel at that. I wonder if it's impossible to use the newer ones like that. Anyone has any experience? Asking because our neighbors want the same great "tv".
I have to agree, simply not buying LG isn't an option, we'd have to rule out just about everyone for the same reason.
I have a slightly older WebOS LG TV, it has PS5, Switch 2, and FireStick 4K Max and an Onkyo receiver plugged in, and as an OLED TV it's incredible, LG would always be my first choice for picture. Don't care about built-in sound as I use a sound-system.
Right now I'm in the market for another TV at around 65inches and was looking at the 2025 model LG OLED, I likely won't connect it to the internet and will probably just hook up an Apple TV following some discussion in another comment section about how much I hate my Fire TV for being ad-ridden.
Really I wish LG or someone would just make a dumb TV with 4+ HDMI, ARC, perhaps DP and a remote and let us hook up what we want; but it'll never happen.
This is my plan for beginning of new year (42" model), mixed games & desktop usage (I know oled ain't best for windows work but non-oled gaming monitors are rather crap ie due to non ideal local dimming, ghosting, mediocre colors compared to oled and so on).
Didnt plan on making it also a TV with internet connection, now I darn sure as hell won't.
Its really sad state of things that the best course of action now for new hardware is to simply use it as it is, never update or plug online since for any chance of any minor issue being fixed there is 100x the risk it will go to shit in substantial ways (I have Samsung q990d - they soundbar literally dying for good after an official update, but that one you had to at least push yourself from phone or via usb).
Not possible with everything, or at least not without substantial hacking for many.
That seems a bit of an overreaction. The top 10 front loading washing machines on Consumer Reports' rating list are 8 LGs followed by a Samsung and another LG.
If you don't want WiFi you can still get a top rated washer. The LG WM3400CW, which is in a 3 way tie for high score, does not have WiFi (or Bluetooth, or any other radio).
Note: Consumer Reports says that it does have WiFi but they are mistaken. It does have LG's "SmartDiagnosis" which lets you view diagnostic data in their app which is probably what confused them. On models with WiFi the app gets the data via the network.
On the 3400 you press some buttons on the washer to tell it to send diagnostics, and then it sends them acoustically similar to the way analog modems sent data. You tell their app to use the mic to listen to that and decode the data.
The WM3470CW, #10 on the Consumer Reports list, also is radio free and uses sound for SmartDiagnosis. Consumer Reports correctly lists this one as not having WiFi.
That's the problem. Front-loading washers have generally been a terrible invention. Unbalancing and mold are among the widespread problems. The actually reliable washers are still top-load.
I've always wondered, since we only have front-load washers here in the UK, is there some sort of advantage to it, aside from space, which seems to be the obvious one, does gravity help with battering the clothes around when the drum spins slowly enough they can fall from the top of the drum?
Front loaders are gentler on clothes, use a lot less water, use a lot less energy, and spin faster in the spin cycle so there is less work for your dryer if you use one.
Top loaders are easier to load and unload, cheaper, and slightly easier to maintain.
With front loaders you should wipe the gasket after use because water left in its folds can promote mold and odors. With both you should leave the door open when not in use so air can circulate in the drum. With a front loader the open door can get in the way and is easier to accidentally close.
Interesting, thanks, I had no idea about much of this, I was aware of the door/mould thing, and stacking, though it's not something I've ever seen done here in the UK personally.
As a "typical" British household, we don't use a dryer, don't even own one in fact, we just hang our clothes to dry, which always struck me as ironic for such a humid, cold country, with smaller (than the US) homes and thus less space to hang stuff to dry.
It’s funny, I never connected my G5 to the network or accepted any of the optional T&Cs, so there’s now numerous places in the UI that say “accept terms to see personalised content”.
Just to be clear, they are NOT deactivating IntelliSense which suggests classes and functions.
This is an AI inline code suggestion tool using local LLMs.
Not great but may or may not impact your workflow. I love using agents, but Intellijs inline code suggestions (also based on a local LLMs) are usually useless to me.
If anyone is considering moving editors, I was recently in the same boat and I can’t recommend enough lazyvim + the ebook “lazyvim for ambitious developers”.
This gets you a fully featured vscode-like baseline (navigation, language integration, integrated terminal, the whole thing).
I had tried many times to switch to vim/emacs and the initial barrier to get a workable system always kept me from pushing forward. With this I was able to make neovim my daily driver at work after just a couple weekends playing with it.
I felt the same way about vim. I never had the patience to get started and configure everything to get the full benefits.
I just switched over to Omarchy for my personal OS and I know that it comes with a pre-configured neovim (using lazyvim) setup that looks like a fully-fledged IDE.
I personally have been using Helix as my editor at home and work. The fact that everything generally works on download is what got me using it.
I think some of the big features of VSCode are the extensions and, equivalently, the nice debug support. I just started using VSCode about a week ago thanks to moving to a project that uses scons as its primary supported build tool, and I've learned to hate scons and love VSCode over that time. The completely manual tasks/launch/etc stuff is kind of weird at first, but then becomes amazing and far more convenient, after you get used to it. And the 'debugger' (kind of weird to frame it that way as its extension based, like everything) is amazing - extremely fast, great visualizations, and so on.
I can't help you much, as currently I happen to use ruby at work and native debugging is enough - you can drop into an interactive console at a breaking point adding a single line, with no tooling.
> I happen to use ruby at work and native debugging is enough - you can drop into an interactive console at a breaking point adding a single line, with no tooling.
If you've only ever used this type of debugging, you should really try out a real IDE debugger once. The difference in productivity when you can use your IDE to navigate to, say, the usages of a function and then just press a keyboard shortcut to put a breakpoint on the line with that usage is immense.
Compare this to the native debug support: you have to leave the interactive debugger, move to your editor, find usages, note down the file name and line number, then go back to your interactive debugger and type a manual break command (break my_file.rb:2517 or something). All of that context switching and remembering is replaced by a single keyboard shortcut in Emacs, VS Code, or any other integrated debugger. And no, adding manual breakpoints in your source code is not simpler - what I'm describing works interactively while your code is already running, whereas a breakpoint statement requires you to restart the whole process.
>If you've only ever used this type of debugging, you should really try out a real IDE debugger once.
It's the opposite, I learned to program with java for android so a full IDE was my first experience. As I moved to node and then go and ruby I just gradually used it less and less as I generally 'debug' creating tests to check/reproduce behavior.
I do think I should improve my debugging, but mostly in terms of profiling. I very rarely feel the need to see a codepath run line by line.
I'm not saying my system is better or worse to be clear, I've just naturally gravitated to not using the debugger - I couldn't tell you why.
This is exactly what I meant by an integrated debugger. I probably should have used the term IDE less, as that brings to mind Visual Studio or Eclipse and such - but I just meant any integrated editor+debugger, whether neovim, Emacs, or whatever else.
And sadly it is also not accessible to screen readers. VS Code for all its flaws is really, really good for screen reader accessibility. In fact, I'd go as far as to say that it's not only one of the most accessible code editors we have, but one of the most accessible electron apps overall. So losing it to this Microsoft stuff would be a huge deal to anyone who relies on screen reader or accessibility tools. :(
The reason I didn't explore Zed is their for profit model.
There might be awesome people and work behind it now, but I've already been burned enough times by rug pulls and shittyfication. I don't want to be planning another move 5 years from now.
I suggest the opposite and not starting with all the plugins and instead try to learn the vim way of doing things. Being too locked in to the old ways could prevent discovering all the great things vim can do.
The examples you mention already exist.
- navigation: plenty of native navigation in neovim, does lazy add anything specific?
- language integration: lsp, requires config sure but git clone isn't much work.
- integrated terminal: just run `:term`
Learning to think in vim means unlearning a lot of old habits. Today I only use fzf.vim, nvim-lspconfig and a theme, not even a plugin manager (I will migrate to the native one that's in nightly when it reaches stable though). Pretty much vanilla Neovim. I'm considering trying nvim-dap to get better debugger support but so far I'm fine with :termdebug for the languages it supports (c/go/rust just works).
When I find something I want vim to do I start with a keybinding, then a function, and maybe if it's complex add a plugin. Adding half of the available plugins just because creates an unnecessary attack vector you now have to keep an eye on.
I do get the benefit of not depending on plugins, really. Long term my current config could rot (abandoned projects, moving dependencies, etc), while a simple config is stable. But I'm happy removing dependencies one at a time.
For example, <leader> ft toggles a terminal in a bottom split. This is familiar enough that I knew I could rely on it whenever needed.
Could I have used :term and manually set splits each time? or learn tmux? or use ctrl+z and fg to move back and forth ? Sure, but that's extra cognitive load.
Maybe I want to focus first on becoming fluid with regex for search and replace, or improving the flow for running unit tests, or get used to using macros as a replacement for multicursor. There's a lot of gaps to cover, each small enough that it's "just do X" for a veteran, but enough when added up that I would much rather pay the cost gradually.
> Could I have used :term and manually set splits each time?
That's when you know you want to create a keybinding, here's a suggestion that opens a split below the current window with 10% height and starts a terminal: `nnoremap <leader>ft :belowright 10 split | terminal<CR>`
But is a terminal really what you want or do you just want to run a command? Maybe just `:!command` is enough 9/10 times that you reach for <leader>ft? In that case a common binding is `nnoremap ! :!` which puts you in that mode with a single key.
> get used to using macros as a replacement for multicursor
This exact example was how I realized the vim way is better than my assumptions. I used to install a multicursor plugin and bind to Ctrl+d because that's what I knew. When I learned macros and s/old/new it became irrelevant.
You seem to already know a lot of the possibilities that you can learn, I didn't and discoverability in vim isn't great. So I just forced myself to search for whatever I didn't know how to achieve and many times ended up learning something extremely powerful.
Today I have all sorts of useful little functions, <leader>m is make, or gcc if no Makefile exists. And now I've extended it to generate mermaid charts in markdown files and open them in my imageviewer and so on.
That's the true power of vim to me, adding standard tools from the system in keybindings and just getting it to do things MY WAY, not how I was taught it should work. It follows the unix philosophy and batteries included is by definition not part of that mentality.
Same with Emacs. Needs some feature? Just write something quick in Elisp and have a new command. The primitives are versatile and a lot of tasks can be reduced to a few commands instead of a long interaction with the terminal/GUI.
>What people often defines as workable system is replicating their old editors instead of learning the current one. Like adding a file tree on the side
Well, kinda. I define a workable system as a system I, personally, can work with straight away, with a minimum loss of productivity. It is not at all meant as a judgement on how good plain vim/emacs are.
This workability indeed might require temporally replicating old habits while I learn the new ones, which lazyvim does. Vscode-like file trees, global search, or integrated terminal, for example.
It's also about discoverability, like the helpers shown through which-key. And the guarantee that a set of default plugins play well with each other, so that I can leave toying with the config for whenever I have the time.
Some people might think this is a crutch for properly learning the tool, but this is not my experience. I'm much more likely to get comfortable with vim and learn further if I can be in it 8 hours a day from the start. At first I used the integrated terminal to run git commands, now I invoke lazygit, which I love. At first I used the file tree to navigate, now I have custom commands to bring a file and its test suite side to side on a keypress. This gradual curve is what I was missing earlier.
Yeah, for most of us in the real world, we can't afford to be way underproductive for a week while we learn and set up our new editor from scratch. Learning vim is one of the greatest gifts I think I gave myself, and I'm extremely glad I did it, but it was not easy. A more gradual curve or even a crutch is completely fine in my opinion. I've seen plenty of people get started with vim just by putting them key bindings in their IDE and getting used to the motions, and then gradually moving over. The main key is to iterate, and not stagnate
> This workability indeed might require temporally replicating old habits while I learn the new ones, which lazyvim does
I'm not judging your for it, but to me that sounds like learning the violin by plucking the strings like a guitar. You're increasing the learning period by following old habits which may even be harmful.
I think it's better to just use the new editor sparingly, learning what you need, then switch fully once you're comfortable. A filetree is never necessary unless you're actually exploring and a file manager would be better for that. Vim has global search with `grep` and the terminal is available through `ctrl-z` and the `:terminal` command.
I've seen people touting Neovim setup that are just making things complex and fragile for no reason.
>that sounds like learning the violin by plucking the strings like a guitar.
I'd compare it more to learning photography without going for manual aperture and developing analog film straight away. You'll have a better experience if you learn stuff like framing with an automated camera that frees you to shoot a hundred pictures daily and focus on a certain skill.
I am increasing the learning period, that much is true. But if I can make use of my daily 8 hours of work as practice, that makes up for the delay, because I can get much more practice.
Maybe a student or a hobbyist can afford to spend 3 minutes nailing the regex while they learn to search and replace, I just can't be fighting that kind of friction regularly at work.
IMO, it’s still the wwrong approach. Vim and Emacs are just editors. Very much like Notepad. You don’t have to learn the extra stuff.
Once you are comfortable with basic notepad-like usage, you can then learn more advanced features. But emacs and vim are different from VSCode because those advanced things are supposed to be tweaked to personal preferences, not be handed down from high. When you start with something like Lazyvim, you’re missing on everything that makes vim, vim. You just have a walmart version of VSCode.
Learning an entirely new editor is a barrier. Documentation or not, that's brand new muscle memory you have to develop alongside the actual task of coding.
I get that using vim typically includes obsessive forms of efficiency, but some people just want to focus on coding in a way that's comfortable to them. Sometimes that means having a side panel.
> Honest question, what is it that you hate about modal editing?
It's annoying. I'm fine with being in one mode. I'm fine with selecting 7 lines and typing "whatever". I hate "7ddiwhatever<esc>".
And yes, it may be the case that you are faster in VI(m) than I am in (choose the editor) but that doesn't matter. For me speed of typing is never critical.
I tried Helix and Kakoune too. They all have the same problems.
First. It adds friction. Every damn time I need to write, I forget to enter insert mode. You have no idea how many times I ended up with a strange buffer. Hopefully there is undo. But it gets boring fast. I need to write as soon I enter the editor. I don't need to move the cursor to read the text that visible on the current page.
Second, how the hell I'm supposed to make small movements when I'm in insert mode, with the arrow keys? Like move cursor to the left by 3 chars. Do I enter normal mode, press l 3 times. Or delete the whole word and rewrite it?
Third. Why some movements are symbols? Like, line ending is $. Beginning of line is 0. so much so for home row movements.
Fourth. Could never remember if f or t includes the char I'm looking for.
Fifth. How cumbersome is to press ESC on the top left corner every damn time. Yes, there exists Ctrl+[. But still. So much so - again - homerow movement.
Not directly related to modal editing.
Sixth. I could not make copy/paste work reliably in remote a linux server from a Windows machine via SSH. Hell, I could not make it work with WSL2.
Sevent. Debuggers sucks. There is no comparison to JetBrains Debugger GUI. Not even VSCode come close to it.
The rant is fine. I'll just provide some explanation.
First: Vim comes from vi, which is a visual mode for ex, which is a supercharged version of ed, which is (the standard editor) a line editor. With ed, you don't really write, you issue commands that does things to the file. Think of the file as a long roll of paper and the program as an assistant. So a command could be "replace your on line 14 with you're" or "delete line 34 to 45". Ex added more commands, Vi made it interactive, and Vim added even more features (syntax highlighting, scripting, location list,...). But still the same mode of interaction remains. The cursor is what you control. It's not just an indicator where the next character will appear or be deleted. It's the starting point of more powerful interactions.
Second. You're not supposed to move the cursor that much in insert mode. For 3 characters to the left, I just backspace and rewrite. For more, I go to normal mode and use F, f, T, or t which will land me to the character I want. Then I can use something like x (delete character) or r (replace character) without having to enter insert mode. There's a lot of movement beside hjkl, and I rarely uses h or l for things that further away than two characters.
Third. There's not a lot of key on the keyboard. $ is end of line in most regex dialect, ^ is beginning of line which would be actually the first character, but most people would assume it's the first non-whitespace character, so that's how they went. In C, curly braces mark blocks of code, so it's a small leap to use it for blocks of text, aka paragraphs.
Fourth. My mnemonics are f (find) and t (to). The latter does not include the character.
Firth. A lot of people remaps the caps lock to either Ctrl or ESC.
Sixth. They're different computers so there's no shared clipboard. Sharing information between the clipboard can be done using escape sequences, but I've never bother to. I just maximize the current buffer so I can use the terminal selection. And if I wanted more than a screen (dmesg), I'd pipe the command to a file and then download that file with sftp.
Seventh. Jetbrains only have debuggers for a handful of programming languages while `printf` is universal. And there's no law forbidding installing an IDE alongside your editor.
I had tried many times to switch to vim/emacs and the initial barrier
to get a workable system always kept me from pushing forward.
For me Helix gets enough right out of the box I find myself reaching for it far more than I ever did with vi or Emacs. They're working on plugin support but I've not felt the need to investigate it at all.
Is there a good solution to managing "workspace", especially handling multi-folder workspace? I have a project where code lives in giant monorepo, and the files I edit don't have the same root (more precisely, the root is too large to open in the editor). I haven't found a good solution outside VSCode yet.
How about switching from VS Code to VS Codium? Same experience without the microsoft telemetry. I suppose Copilot won't be included due to licensing constraints.
How does the extension model work with MS? I did a similar move to chromium and eventually had to move to firefox when they pulled the plug on ad blockers.
ITT: gross overreaction, as usual. IntelliCode is NOT IntelliSense. They're obviously not removing traditional autocomplete.
They're replacing an EXTENSION, so it has basically nothing to do with VSCode itself. If they developed an "IntelliCode for Vim" plugin, they would also replace "IntelliCode for Vim" with Copilot.
I refuse to use VS Code on principle. It has captured a staggering percentage of software development, across many software disciplines. Somehow ARM/Keil has been persuaded to go all-in on VS Code and will deprecate their "legacy" IDE, which will cause trouble for any hold-out embedded firmware developers.
> It has captured a staggering percentage of software development
In hindsight it's obvious why: it was the only free editor that has a product mindset and a product team behind. Microsoft put heavy hitters on it, some of their best engineers, treated it as some companies treat their core products.
Other IDEs/editors are mostly open source with no real direction and resources, or are proprietary expensive software.
It's unfortunate but to compete with VS Code you need a lot.
I'm so happy I made the jump to NeoVim 6 months ago.
I finally got good RTL support with iTerm, language server stuff works great, and best of all, navigating and selecting things SYNTACTICALLY with nvim-treesitter-textobjects is life-changing.
I wonder if this will also impact VSCodium. I use it specifically to avoid a lot of the crap that Microsoft is trying to do while still being able to use the editor and plugins.
They have not released 1.107 yet, doing a quick scan I am not seeing anything on the VSCodium github.
Intellicode being (officially) deprecated will impact VSCodium, yes. I too am more concerned about copilot being further “needed” or required in my VSCode fork. It’s already the biggest pain in the butt I’ve ever had to deal with in the context of VSCodium. I am not excited for the future.
I didn’t think it was even possible to install proprietary microsoft extensions in VSCodium, how is that related to the version of the editor and how would it affect VSCodium?
Right. Then the removal of this IntelliCode extension from MS should have no effect on VSCodium users.
I thought originally it may have been an OSS extension, but it actually seems to have been a proprietary project licensed under the Microsoft Software License, similar to Copilot and such.
Probably targeted at enterprise customers forcing them embrace co-pilot with big pockets. Bad move for individual users as this will only drive them to alternatives, instead of shelling out money.
Unfortunately, people often resist change and prefer to stick with what they know. Maybe a small percentage of people will look for alternatives but it'd be a drop in the ocean.
I don’t really get the issue, I didn’t even know Microsoft published another AI suggestion extension, definitely cool that it used a local model but it does make sense for them to just roll it into Copilot.
IntelliCode was first released in 2018, well before the current AI landscape. The issue here is taking a free, functioning capability and arbitrarily disabling it in favour of a paid product. Microsoft is currently "updating" its internal adoption goals for the AI features it keeps shoving down consumers throats, but I'm sure that pumping the numbers by removing features is surely just coincidental and not desperate at all.
Great there are other true open-source tools to be used zed, nvim.
I also noticed that copilot nowadays is forcing you to upgrade to their with following text:
"You've reached your monthly code completion limit. Upgrade your plan to Copilot Pro (30-day Free Trial) or wait until 2025-12-19 for your limit to reset to continue coding with GitHub Copilot"
Was using it actually like smarter auto-completion. But paying for that, hell no.
> Great there are other true open-source tools to be used zed, nvim
without going into the actual qualities of the editor, they simply lack extension support, for now.
In the embedded space, many manufacturers have switched - or are switching - to a suite of VSCode plugins and gradually discontinued the previous tools. Which is great on one hand: they don't have to keep supporting heavily modified IDEs from 10 or 20 years ago and they can better integrate with the rest of the ecosystem of plugins, scripts automation and such. LSP has been a good thing.
The problem is that you are now at the mercy of microsoft not fucking up with the environment at every other release. To put it simply, we are screwed. And i tried for so long not to use it because i knew this day would come, but it's just so much better.
And no, i will not just use a text editor and a makefile. I want an IDE. IDEs are good, when they seamlessly integrate with tools.
Had a shower thought about how much I am starting to dislike vscode now that every minor version just loads on unwanted copilot cruft instead of adding actual features. Grabbed nvim that night.
I had a scare combined with an insight last week. I was looking for documentation on power BI - specifically the M language. I found the Microsoft documentation but found it to be much more sparse than I hadremembered It only had the function names and the argument names and almost no explanation.
I thought "what a perfect way for Microsoft to force copilot upon us". They can make it necessary by being the only "documentation" of their software.
VS Code feels like nothing but bloat. Sublime Text is still my go-to, as I'm not very well-versed in Neovim yet. I'm also really digging the new C/Lua-based Lite XL - https://lite-xl.com. One of my New Year's resolutions is to learn Neovim properly.
Try Zed. Open-source (GPL+Apache), reliable, fast, not bloated at all, decently configurable, amazing remote-host support, Vim mode, AI stuff totally optional, extensions/lang-servers available for many languages, and... well overall I find it very neat and polished!
(I'm not associated with Zed, just a happy user looking to share the goodness.)
I've been using Zed for about a month and I'm very happy with performance the features. It guides you to setup only what you need, that was a problem with VSCode that would collect random plugins through time. I work regularly with Go, React, TypeScript, and I don't miss VSCode.
90% of the reason I use VSCode is the extensions. Zed doesn't have the ecosystem.
For VSCode I can get the official extension by the actual company doing $thing. With Zed I need to trust Random Person's extension that it doesn't have spyware or keyloggers in it.
"but but the company could!" yes, but they have a reputation to protect, releasing an official extension that leaks data is Very Bad. Random Person (if that's their real name) doesn't care, or does. I have no way of telling.
Copilot is what finally pushed me to use vim seriously. There's not a single thing I miss from VS Code, or Visual Studio, and I'm not even using neovim. Also dropped .NET, which I've used professionally since Framework 1.0, in favor of Go. Don't miss anything from there either.
Not even EF Core? C# pattern matching and switch expressions? Linq? I find these very hard not to miss when working in other langs. C# is a fantastic programming language nowadays.
IMO no ORM. I've only had issues with ORMs. They work okay-ish in the very bare-bones usecases, like inserting one record into one table or fetching one record. After that, their semantics just impede your velocity.
You can represent really, really complex data retrieval and consolidation semantics in SQL. ORMs are really more of an organizational tool in my mind.
I just throw all the SQL functions into a repository class around one "thing". Not even object, it can be related functionality or operations.
SQL in code can be awful, if spread out across your codebase. So I think just don't do that.
We have a monolith that gets maybe ~1000 commits a day. We don't use an ORM, just SQL and query builders. It works out if you have good modularization.
can anyone recomend a alternative that is easy to install and also offers syntax highlighting? i have read about lazyvim and neovim, but both have extensive install requirments as i have read
If you really only care about syntax highlighting then nearly any code editor will do. Even nano supports it, it’s just disabled by default.
If you want something powerful yet easy to pick up, you might want to look at e.g. Zed (GUI IDE), Sublime Text (GUI editor), or Micro (TUI editor). If you don’t mind a learning curve, Vim/Neovim and Emacs are excellent choices. But there’s a lot of other options out there, like Gedit, Kate, BBEdit, Notepad++, etc. depending on your platform of choice.
I've been having a very good time with Zed. Great vim motion support, and fast to the point where using VSCode feels like driving a semi truck by comparison.
For TUI, Helix has a lovely out-of-the-box experience. What little config there is (two TOML files) is relatively easy to grasp. The main barrier you'll face is setting up your LSPs, which need to be installed manually. (Luckily, there's `uvx -q` for Python LSPs.)
For GUI, Zed is also really nice, has a great Vim mode, and auto-installs anything you might need. It loses a couple of points to VS Code on account of not being arbitrarily extensible, although that can also be seen as a plus, as it prevents extensions from randomly slowing everything down.
I’ve been using Zed [1] for some time now. They are also pretty AI focused so it may only be a matter of time, but so far I’ve been able to disable all of the AI interactions.
Kate is such a refreshing change. Super responsive and fast under Asahi. It's the best dev environment I've worked with in a very long time.
A few niggles with the switch, like it seems to assume Git but I'm using Fossil. I also haven't found a decent cheat-sheet for keyboard controls. I got duplicate block and move block working, and really enjoy the column editing, but still using cut for line delete.
I think KWrite is the same engine underneath? at least it feels much akin to Kate. I use it mainly for assembly files, since I was able to hack in an armv8 syntax file and needed a different theme than Kate.
VSCodium has been my go-to. VS Code was great for a bit but (even long before this) it was already suffering from the cancer that is "being a microsoft product" and it was being bloated to death like everything else they ship, but VSCodium seems to keep enough distance to be immune. Will it stay that way? Who's to say. I hope so though.
+1 on VSCodium. It was a 99.99% seamless transition, for me. The only annoyance at all was not having VSCodium added to my context menu, which doesn't even matter if you never "right-click->open folder" to launch. And, obviously, is pretty easy to add back in both windows and linux.
If you follow the link in the articla you can see that this is, specifically, Intellicode for C#. This is not the standard language server protocol stuff, which continues to exist just fine.
I've often thought, "If AI is so great, how come all these tech companies are shoving AI features down our throats for free, instead of charging real money for them?" I'm actually glad that MS is doing this, and I hope it starts a trend of more companies gating their AI features behind paywalls, and a noticable reduction in the number of popups I encounter badgering me to use AI features that I never asked for.
IntelliCode was first released in 2018, well before the current AI landscape where running each model costs a neighborhood's worth of power. Indeed, it runs using a small local model that costs essentially nothing in comparison to the rest of the machine running it.
In fact, the intent here is exactly the opposite of what you're hoping for (less AI badgering). They're trying to get people to actually use Copilot after recently missing internal adoption goals on all the AI products they're trying to shove down people's throats. The badgering is only going to get worse, and they're going to continue removing functioning, free features to do so. You should not be glad that Microsoft is killing a free lightweight product for a bloated, ecologically harmful and economically wasteful one.
I believe this comment is nuts. How the hell are you justifying the removal of a free and common IDE functionality for something that it's rate limited based on usage? In any other context, this would have been called enshittification...
If anyone else would be generous enough to offer a free IDE with free AI code completion, they could give VS Code a run for its money, but as far as I know this hasn't happened yet? Zed for instance is available for free, very AI-centric, and you can use it with any of the popular LLMs, but you still have to pay for the LLM...
Bring your own AI token is totally fair, given the cost of AI.
The annoying thing is removing a perfectly working intellisense default.
If Jetbrains removes their on-device (non-AI) code indexer and suggestion systems then I will no longer be a paying customer for example. Despite being a All Products Pack user for the last... idk, 15 years?
I use both but really don't see it. There are so many scenarios I've come across which jetbrains products do "out of the box" that vscode require plugins which usually don't install with sensible defaults. Just debugging rust for example is a night and day difference between vscode and rust rover.
> It's a plugin that I'm not using, don't care about using, and cannot see any conceivable use for.
> No-one wants this.
So, fun fact about earth: there are lots of people on it, and some of those people aren't you, and some of those people who aren't you actually have desires that are different from yours.
I think it makes the planet a pretty fun and interesting place, but it also does mean generalizing from "I don't want this" (totally fine! Awesome! Makes sense!) to "no one wants this" is usually not very productive.
IntelliCode has 60M downloads and is the 11th most downloaded extension for all of VS Code. Also consider that there's 6 official Python-related extensions above it that could all be rolled into one, and Copilot just above it which (to my knowledge) is installed by default in newer versions of VS Code.
Just because it doesn't affect you personally doesn't mean it affects no one. You aren't in fact the centre of the universe.
I'm guessing that's 60 million people that don't have a small child that can just type stuff that looks kind of like code but doesn't actually work like code.
Expect the amount of f*ckery to increase as the AI realities set in but the number has to go up either way.
It reminds me of the good old days of Visual Studio + .NET + SQL Server where they played these games too.
reply