7 ms·

VSCode is based on Chromium. https://chromium.googlesource.com/chromium/src/+/HEAD/docs/vscode.md https://chromium.googlesource.com/chromium/src/+/HEAD/docs/v..

VSCode is based on Chromium. https://chromium.googlesource.com/chromium/src/+/HEAD/docs/vscode.md https://chromium.googlesource.com/chromium/src/+/HEAD/docs/v...

lokimedes 10mo ago
Which is based on Apple Webkit? The winner is always the last marketable brand.
- onion2k 10mo ago
  That drives exactly $0 of Apple's revenue. It's only a win if you care about things that don't matter.
  - hu3 10mo ago
    And Apple is not even the last node in the chain. WebKit came from KDE's khtml Every year is the year of Linux.
- usrnm 10mo ago
  Both are based on khtml. We could be living in a very different world if all that effort stayed inside the KDE ecosystem
  - embedding-shape 10mo ago
    Which came from "the KDE HTML Widget" AKA khtmlw. Wonder if that's the furthest we can go? > if all that effort stayed inside the KDE ecosystem Probably nowhere, people rather not do anything that contribute to something that does decisions they disagree with. Forking is beautiful, and I think improves things more than it hurts. Think of all the things we wouldn't have if it wasn't for forking projects :)
    - Dylan16807 10mo ago
      On the other hand if that had stopped google from having a browser they push into total dominance with the help of sleazy methods, maybe that would have been better overall.
      - lukan 10mo ago
        I still prefer a open source chromium base vs a proprietary IE (or whatever else) Web Engine dominating. (Fixing IE6 issues was no fun) Also I do believe, the main reason chrome got dominance is simply because it got better from a technical POV. I started webdev on FF with firebug. But at some point chrome just got faster with superior dev tools. And their dev tools kept improving while FF stagnated and rather started and maintained u related social campaigns and otherwise engaged with shady tracking as well.
        Dylan16807 10mo ago
        > I still prefer a open source chromium base vs a proprietary IE (or whatever else) Web Engine dominating. Okay but that's not the tradeoff I was suggesting for consideration. Ideally nothing would have dominated, but if something was going to win I don't think it would have been IE retaking all of firefox's ground. And while I liked Opera at the time, that takeover is even less likely. > Also I do believe, the main reason chrome got dominance is simply because it got better from a technical POV. Partly it was technical prowess. But google pushing it on their web pages and paying to put an "install chrome" checkbox into the installers of unrelated programs was a big factor in chrome not just spreading but taking over.
        Zardoz84 10mo ago
        > And their dev tools kept improving while FF stagnated and rather started and maintained u related social campaigns and otherwise engaged with shady tracking as well. Since when you don't touch Firefox or try the dev tools ?
        lukan 10mo ago
  - josephg 10mo ago
    > Both are based on khtml. We could be living in a very different world if all that effort stayed inside the KDE ecosystem How so? Do you think thousands of googlers and apple engineers could be reasonably managed by some KDE opensource contributors? Or do you imagine google and apple would have taken over KDE? (Does anyone want that? Sounds horrible.)
    - sheepscreek 10mo ago
      I think they meant we wouldn’t have had Safari, Chrome, Node, Electron, VSCode, Obsidian? Maybe no TyeScript or React either (before V8, JavaScript engines sucked). The world might have adopted more of Mozilla.
- benoau 10mo ago
  It's "based on WebKit" like English is based on Germanic languages.
  - antonvs 10mo ago
    English is a Germanic language. It’s part of the West Germanic branch of the Germanic family of languages.
  - master-lincoln 10mo ago
    This fact adds nothing to the discussion
- dragonwriter 10mo ago
  Note that these are somewhat different kinds of "based on". Chromium is an upstream dependency (by way of Electron) for VSCode. WebKit was an upstream dependency of Chromium, but is no more since the Blink/WebKit hard fork.
- znort_ 10mo ago
  that's a bit misleading. it was based on webcore which apple had forked from khtml. however google found apple's addition to be a drag and i think very little of it (if anything at all, besides the khtml foundation) survived "the great cleanup" and rewrite that became blink. so actually webkit was a just transitional phase that led to a dead end and it is more accurate to say that blink is based on khtml.
dragonwriter 10mo ago
VSCode is Electron based which, yes, is based on Chromium. But the page you link to isn't about that, its about using VSCode as dev environment for working on Chromium, so I don't know why you linked it in this context.

VSCode is based on Chromium. https://chromium.googlesource.com/chromium/src/+/HEAD/docs/vscode.md https://chromium.googlesource.com/chromium/src/+/HEAD/docs/v...

lokimedes 10mo ago

Which is based on Apple Webkit? The winner is always the last marketable brand.

onion2k 10mo ago
That drives exactly $0 of Apple's revenue. It's only a win if you care about things that don't matter.
- hu3 10mo ago
  And Apple is not even the last node in the chain. WebKit came from KDE's khtml Every year is the year of Linux.
usrnm 10mo ago
Both are based on khtml. We could be living in a very different world if all that effort stayed inside the KDE ecosystem
- embedding-shape 10mo ago
  Which came from "the KDE HTML Widget" AKA khtmlw. Wonder if that's the furthest we can go? > if all that effort stayed inside the KDE ecosystem Probably nowhere, people rather not do anything that contribute to something that does decisions they disagree with. Forking is beautiful, and I think improves things more than it hurts. Think of all the things we wouldn't have if it wasn't for forking projects :)
  - Dylan16807 10mo ago
    On the other hand if that had stopped google from having a browser they push into total dominance with the help of sleazy methods, maybe that would have been better overall.
    - lukan 10mo ago
      I still prefer a open source chromium base vs a proprietary IE (or whatever else) Web Engine dominating. (Fixing IE6 issues was no fun) Also I do believe, the main reason chrome got dominance is simply because it got better from a technical POV. I started webdev on FF with firebug. But at some point chrome just got faster with superior dev tools. And their dev tools kept improving while FF stagnated and rather started and maintained u related social campaigns and otherwise engaged with shady tracking as well.
      - Dylan16807 10mo ago
        > I still prefer a open source chromium base vs a proprietary IE (or whatever else) Web Engine dominating. Okay but that's not the tradeoff I was suggesting for consideration. Ideally nothing would have dominated, but if something was going to win I don't think it would have been IE retaking all of firefox's ground. And while I liked Opera at the time, that takeover is even less likely. > Also I do believe, the main reason chrome got dominance is simply because it got better from a technical POV. Partly it was technical prowess. But google pushing it on their web pages and paying to put an "install chrome" checkbox into the installers of unrelated programs was a big factor in chrome not just spreading but taking over.
      - Zardoz84 10mo ago
        > And their dev tools kept improving while FF stagnated and rather started and maintained u related social campaigns and otherwise engaged with shady tracking as well. Since when you don't touch Firefox or try the dev tools ?
        lukan 10mo ago
- josephg 10mo ago
  > Both are based on khtml. We could be living in a very different world if all that effort stayed inside the KDE ecosystem How so? Do you think thousands of googlers and apple engineers could be reasonably managed by some KDE opensource contributors? Or do you imagine google and apple would have taken over KDE? (Does anyone want that? Sounds horrible.)
  - sheepscreek 10mo ago
    I think they meant we wouldn’t have had Safari, Chrome, Node, Electron, VSCode, Obsidian? Maybe no TyeScript or React either (before V8, JavaScript engines sucked). The world might have adopted more of Mozilla.
benoau 10mo ago
It's "based on WebKit" like English is based on Germanic languages.
- antonvs 10mo ago
  English is a Germanic language. It’s part of the West Germanic branch of the Germanic family of languages.
- master-lincoln 10mo ago
  This fact adds nothing to the discussion
dragonwriter 10mo ago
Note that these are somewhat different kinds of "based on". Chromium is an upstream dependency (by way of Electron) for VSCode. WebKit was an upstream dependency of Chromium, but is no more since the Blink/WebKit hard fork.
znort_ 10mo ago
that's a bit misleading. it was based on webcore which apple had forked from khtml. however google found apple's addition to be a drag and i think very little of it (if anything at all, besides the khtml foundation) survived "the great cleanup" and rewrite that became blink. so actually webkit was a just transitional phase that led to a dead end and it is more accurate to say that blink is based on khtml.

dragonwriter 10mo ago

VSCode is Electron based which, yes, is based on Chromium. But the page you link to isn't about that, its about using VSCode as dev environment for working on Chromium, so I don't know why you linked it in this context.