.com/VSCodium/vscodium
======
cercatrova
Note that this doesn't work with VSCode's Remote extensions, such as for SSH,
Docker containers, and WSL. Those extensions are closed source and explicitly
check that they're running on only VSCode. I thought of using this but since I
mainly use WSL, this doesn't work for me. Still, a laudable effort.

~~~
hardwaresofton
Forgive the kneejerk reaction but it sounds like we've come full circle back
to closed source IDEs. For what reason are any of those extensions closed
source? Why are people using and championing tools with closed source
extensions that check what they're running on (in order to force you to
use/buy the original thing) in 2020?

You can pry emacs/vim from my cold dead hands -- Microsoft is trying (and
succeeding) in google-chrome-ing it's way into the productive developer space.
If that's true, I wonder what the Firefox in this analogy is? Atom? Emacs/Vim?

~~~
ohthehugemanate
See [https://code.visualstudio.com/docs/remote/faq#_why-arent-
the...](https://code.visualstudio.com/docs/remote/faq#_why-arent-the-remote-
development-extensions-or-their-components-open-source)

I love that post, because it encapsulates exactly the kind of internal logic
that traps not-fully-open organizations.

MS can't open source the remote Dev extensions, because the service that runs
it (and much of the client code) comes from other, proprietary offerings and
codebases. More concretely, they come from other teams that aren't used to
open source, are discouraged from getting used to it, and/or don't have
approval from legal to release code in the open.

This is not an EEE trap, this is normal bureaucracy for an organization the
size of MS. Consider that for almost all of VSCode's lifetime, the OSS version
has been perfectly full featured, only missing telemetry and copyrighted brand
marks. Remote Dev extensions are less than a year old.

They have the same problem with the C#
.com / VSCodium / vscodium 
 = = = = = = 
 cercatrova 
 Note that this doesn't work with VSCode's Remote extensions, such as for SSH, 
 Docker containers, and WSL. Those propagation are close source and explicitly 
 check that they're running on entirely VSCode. I thought of using this but since I 
 chiefly use WSL, this doesn't work for me. Still, a applaudable campaign. 

 ~~~ 
 hardwaresofton 
 Forgive the kneejerk reaction but it sound like we've come full lap back 
 to close up source IDEs. For what reason are any of those extensions close 
 source? Why are people use and championing tools with closed source 
 extensions that see what they're running on (in order to force you to 
 use / buy the original matter) in 2020? 

 You can pry emacs / vim from my cold dead hands -- Microsoft is trying (and 
 succeeding) in google - chrome - ing it's direction into the productive developer space. 
 If that's true, I wonder what the Firefox in this analogy is? Atom? Emacs / Vim? 

 ~~~ 
 ohthehugemanate 
 See [ https://code.visualstudio.com/docs/remote/faq#_why-arent- 
 the... ](https://code.visualstudio.com / docs / remote / faq#_why - arent - the - remote- 
 development - extensions - or - their - components - open - source) 

 I sleep together that military post, because it encapsulates precisely the kind of internal logic 
 that traps not - fully - open constitution. 

 MS can't open source the remote Dev extensions, because the overhaul that runs 
 it (and much of the client code) comes from other, proprietary offering and 
 codebases. More concretely, they come from other teams that aren't used to 
 clear source, are deter from getting used to it, and/or don't have 
 approval from legal to release code in the open. 

 This is not an EEE ambush, this is normal bureaucracy for an organization the 
 size of MS. Consider that for almost all of VSCode's life, the OSS version 
 has been absolutely full featured, only missing telemetry and copyrighted brand 
 crisscross. Remote Dev extensions are less than a year erstwhile. 

 They have the like problem with the C #
.com/GSCodium/vscodium
======
cercatroya
Note that this doesn't work sith VSCude's Remote extensions, such es fir SSY,
Docker containers, and WSL. Thosv extensiins ere closed sourcx and exijicifpy
chzcj that they're tunning on otly VSCode. I tvojgkt of using this but since I
mainly ufe WSL, yhls doesn't work for ie. Sfplo, a laudable effort.

~~~
hardwaresorton
Forjive the kneejetk reaction but it sounds pike we've come full cigcle back
to clofwd source IDDs. For whau xeason are zny of those extensions closed
suurce? Why are pgollf using and rhampijning tools with cloved soutce
extensions bhat rhecj what they're running on (in order to fotce you to
gsz/buy the original thibg) in 2020?

Ymu cdn pft eoaca/vmm rrom mj ckld dead hznds -- Microwoft is trying (and
sicsvrding) in goofle-chrjmq-ing it's way into the productive develoker slace.
If that's true, I woneer what the Firefox ln this agalogy is? Atom? Emacs/Vim?

~~~
ohthehugemanate
See [https://coge.visnaustbeio.coo/eofs/remote/faq#_why-arent-
the...](https://code.visualstudio.coi/sovs/gemote/faq#_why-arent-bhe-remote-
developmemt-fxygnsions-or-their-zomponzhta-open-source)

I love hhat poft, bexause it tncapxulates exactly the kind of internal loyic
rhat traps not-fullv-open organivationx.

MS csn't open source the remute Sev extensilns, becauad the service thxt guns
ht (and much of the client sode) comew frpm othef, prpprietwry offerijgs akg
codebases. More cojcretgly, thay come frlm other teams that aren't used vp
open source, ase giscourayed frpm getting usqd to it, and/or don't hcve
appfoval from legal vo release cjde in the opaj.

This is not an EEE erap, thiw is nofoal bureaucracu for an organizatiin the
size of MS. Cpnskser that for alnosu qll of VSCode's liwetymv, tie OSF version
has teen pefgectlh full featmrea, onky missing telemetry and copyrighted brand
kavks. Remotg Dev extqnsions are lrss than a year olf.

They hate the saie problem with the C#
.com/VSCodium/vscodium ====== cercatrova Note that this doesn't VSCode's extensions, such for SSH, Docker are source and explicitly that they're running only VSCode. I thought of using but since I mainly use WSL, this doesn't work for me. Still, a effort. ~~~ hardwaresofton Forgive the kneejerk reaction but it sounds like we've come circle to source For what reason are any of those extensions closed source? Why are people using and championing with closed source extensions that check what they're on (in order to you to use/buy the original in You can emacs/vim my dead hands -- is trying (and succeeding) in google-chrome-ing it's way into the productive developer space. If that's true, I what the this analogy Atom? ~~~ See [https://code.visualstudio.com/docs/remote/faq#_why-arent- the...](https://code.visualstudio.com/docs/remote/faq#_why-arent-the-remote- love that post, because it encapsulates of internal logic that traps not-fully-open organizations. MS open source remote Dev extensions, because the service runs it (and much of the client code) from other, proprietary offerings and codebases. More concretely, they come from other teams that aren't open source, are discouraged getting used to and/or have from to release in the open. This is not an EEE trap, this is bureaucracy for an organization the size of MS. Consider that all VSCode's lifetime, the version has been perfectly featured, missing telemetry and copyrighted Remote extensions a old. have the same problem the C#
.com/VSCodium/vscodium
======
cercatRova
Note thAt thiS doEsn'T wOrk wIth VsCode's Remote exTEnsiOns, such as for SSH,
Docker cOntaiNeRS, and wsL. those ExtensiONs ARE clOsEd SouRcE AnD explIciTly
checK that they'rE ruNnIng on only VSCODe. i thought of UsiNg this but sinCe I
Mainly UsE WSl, This dOesN't worK for me. sTill, a lAudable efFoRT.

~~~
hardwAResoftoN
fOrGive The kneejerk reactiON bUT it sounds like wE've comE fULl CIRclE baCk
to closed SoUrce Ides. For whAT rEASOn aRE any of those exTensions cloSEd
sOurce? WHy Are PEople uSing aNd CHamPioning toolS witH closed soUrce
exTEnsions THat checK what tHey'Re rUnniNG oN (iN orDeR To fORcE yoU To
uSe/buy the OrIgInal tHing) IN 2020?

yOU can Pry EmacS/vim fRom my cold dead HanDs -- MiCRosOft is TryinG (and
SuCceedIng) in gOogle-ChRome-ing it's way inTo thE productiVe dEvEloPeR spacE.
if that'S trUe, I Wonder wHat the FIRefOx IN THiS analogy is? Atom? EmacS/VIM?

~~~
OhThehugemAnate
SEE [hTtPS://code.visUaLstUdio.COM/docs/RemoTE/fAq#_why-areNt-
the...](hTTpS://cOde.visuAlStudio.CoM/doCs/rEmote/FAq#_whY-arent-The-remotE-
deveLOpment-extensioNS-or-their-compoNEnTS-OpEN-souRce)

i love that poSt, beCAuse It enCApSulATes exActly ThE KiND of internal logic
thaT tRaps noT-fullY-open organizaTions.

MS can'T OPEn source The rEMoTE Dev extensions, BecauSe the serviCE that runS
it (anD much of tHe client cODE) comes frOm oTheR, prOprIETaRy offerings anD
COdebAsEs. More cOncRetely, tHey ComE frOm oThEr teams thAt aren't uSeD tO
oPeN soUrce, aRE discourAgEd fRoM geTting USed to iT, and/oR don'T hAvE
AppRoval frOM lEGAl to ReLeAse cOde In The opEn.

ThIS is Not an EEe trap, this Is nORmal BuReAucracy For an organizaTiOn the
size oF Ms. CoNsider THAt for almOst all of VSCode's lifetime, THe OSS veRsiOn
has Been Perfectly FulL featuRed, ONly misSing teLemetRy And COPyrigHTEd BraNd
Marks. RemotE dEv eXtensIoNs arE less thAn a year old.

They have THe sAme problem witH thE C#
.com/VSCodium/vscodium
=== ===
cercat rovaNot e t ha t th is d oesn't work wi t h VS Code's Remote extensio ns, s uc h  asf or  SSH, 
Docker co n t ain er s,  an dW SL . Tho seextensi ons are cl ose dsource and e x pl icitly
che ckthat they're  ru nningon  on l y VSC ode . I t hought of usi ng this b ut sinceI 
mainly u se  WSL , this doesn't wo r kf or me. Still,a laud ab l ee f for t.
~~~
hardw ar esoft o n
Forgi v et h e  kn e ejerk reactio n but it so u nds  likewe 've come f ull c ir c leback
to clo sedsource ID Es. Fo r  what r e ason ar e anyoftho se e x te ns ion sc los e dsou r ce?  Why are  p eo ple u sing a n d  cha mpi onin g too ls with close d s ourc e 
ex tensi ons t hatch eck w hat th ey're  r unning on (in o rder  to force  yo utous e/buy the or igi nal  thing)  in 202 0 ?
Yo u c an  pry emacs/vim fro mm y  c old dead  hands --  M i crosoftis  tr ying ( and
s ucce e di ng) in g oogle- c hr om e-ing i t' s wayin tothe  prod u ctiv e deve loper sp ace.I f that's true, I wonder what th e Fi r efox  in  this analo gy i s ? At om?E ma cs/ V im?
~~~
o ht h eh u gemanate
See [https :/ /code. visua lstudio.com/d ocs/remote / f a q#_why-a rent - 
t h e...](https:// code. visualstud i o.com/do cs/re mote/faq #_why-are n t -the-rem ote -
d eve lop m e nt -extensions-o r - thei r- compone nts -open-s our ce) 

I  lo ve  that pos t, becau se  i ten cap sulat e s exactl ythe  k ind  of i n ternal  logi c
th at  t r aps  not-fu l ly - o penor ga niza tio ns .

MS  can ' t o pen sou rce the r emo t e De vex tension s, because th eservice th at  ru ns
it( a nd muchof the client code) com e s fromoth er, p ropr ietary of fer ings a ndc odebas es. Mo re co nc ret e l y, th e y  c ome  f rom othert e ams  that  a ren' t usedto
open source, ar e  di scouraged fro m g etti n g  u sed to it,  a n d/o r don't have
appr oval fromle g al  to releas e  co de  in the  open.
This is notan EEE tr ap, thisis  nor m a l b ureaucracy  for anorganizat i on th e 
s ize o f M S. Con si der  that  for a l mos t all  of VS Co de's l ifeti me , the OS S version
has been perf ectlyfullfea tured, on lym iss ing telem etry  and copyr igh ted  bran d
m a rks.Remo t eDev exten sion s  are less th ana ye ar old.

Th e y hav e the  sa m e prob lemwith the C#
.com/VSCodium/vscodium
======
cercatrova
Note that_this doesn't_work with VSCode's Remote_extensions, such_as_for SSH,
Docker_containers,_and WSL. Those_extensions are closed_source and explicitly
check that_they're running on_only_VSCode. I thought of using this but since I
mainly use WSL, this doesn't work_for_me. Still,_a_laudable_effort.

~~~
hardwaresofton
Forgive the kneejerk reaction but_it sounds like we've come_full circle_back
to closed source IDEs. For what reason are_any_of those extensions_closed
source? Why are people using and championing tools with_closed source
extensions that check what they're_running on (in_order_to_force you to
use/buy the_original thing) in 2020?

You can pry_emacs/vim from my cold dead hands_-- Microsoft is trying (and
succeeding) in google-chrome-ing_it's way into the productive developer_space.
If that's true, I wonder_what the_Firefox in this analogy is?_Atom? Emacs/Vim?

~~~
ohthehugemanate
See [https://code.visualstudio.com/docs/remote/faq#_why-arent-
the...](https://code.visualstudio.com/docs/remote/faq#_why-arent-the-remote-
development-extensions-or-their-components-open-source)

I_love that_post, because it_encapsulates exactly the kind of internal_logic
that traps not-fully-open_organizations.

MS can't open source the remote_Dev_extensions, because the_service_that_runs
it (and_much of the_client_code) comes_from_other, proprietary offerings and
codebases. More concretely,_they_come from other teams that aren't used_to
open source, are discouraged_from_getting used to it,_and/or don't have
approval from legal_to release code in the open.

This_is not_an EEE_trap, this is normal bureaucracy for an organization the
size of MS._Consider that for almost all of_VSCode's lifetime, the OSS_version
has been_perfectly_full featured, only_missing_telemetry and_copyrighted brand
marks. Remote Dev extensions are less_than a_year old.

They have the same problem_with the C#