Microsoft releases it's own bash terminal now available at the windows store

Microsoft releases it's own bash terminal now available at the windows store

Has anyone on Jow Forums tried this?

devblogs.microsoft.com/commandline/introducing-windows-terminal/

Attached: windowsterminal.jpg (1280x720, 88K)

Other urls found in this thread:

github.com/microsoft/terminal/releases
devblogs.microsoft.com/commandline/introducing-windows-terminal/
twitter.com/SFWRedditGifs

>Microsoft store
No thanks

>bash terminal
what did OP mean by this?

tty i guess

Tried it a while back and hated it because it was a universal windows app meaning the window didn't behave like a standard CMD or Powershell does nor did it work with keybinds like ctrl+w to close a tab. Settings are also stored in a JSON file from what I recall.

This
I don't need ms broken shit
Conhost or whatever it's called is good enough and works
I don't need more bugs on Windows

>Settings are also stored in a JSON
Microsoft has really felt for the JSON meme

github.com/microsoft/terminal/releases

You should like you regurgitate dumbass shit on the regular.

Crashes when you run vim.

Lmfao what a crap
Haha lmao
Use gvim though but vim is good shit too
Microsoft are fags

It's gayer than Mac OS X
Being gay is bad
But being gay and ugly Indian is even worse

>bash terminal
When are they going to release a zsh terminal?

I have no idea what you're blabbering about pajeet

There's literally nothing wrong with settings files being stored in JSON. It's human-readable, what more could you possibly want?

"This winter in 2019, our goal is to launch Windows Terminal 1.0 and we’ll work with the community to ensure it’s ready before we release!"

You just knoi w they are harvesting data off that meta data slippage.

JSON is shit for settings
Only ini style is good for settings
But gui programs should have gui settings
Or they are Reddit gay
Or a turing complete embedded language like vimrc
Fuck XML and fuck JSON

You haven't provided any reasons against it. Just your personal opinion. What's so special about ini configs? JSON is popular and familiar now.

i disagree with being gay is bad, but being an ugly indian is absolutely disgusting.

>What's so special about ini configs?
It's simple
>JSON is popular and familiar now.
It's ugly and bloated and offers no advantage over INI

INI or Turing complete embedded language for initialisation
Everything else is gay

Most settings don't need anything more than
[section]
setting=value

and the added features and syntax of JSON just complicates things

Gay is bad because you get sad and you get aids

JSON is also simple. The only actual disadvantage to JSON configs is the lack of ability to comment, I think config files should be simple and self-documenting though.

>The only actual disadvantage to JSON configs is the lack of ability to comment
HAHAHAHA
WHAT GOOD IS A CONFIG FILE WITHOUT WITHOUT COMMENTS
YOU ARE GAY AND JSON IS AIDS
EVEN XML IS BETTER THAN THIS SHIT BECAUSE EVEN FUCKING XML HAS COMMENTS
FAGGOT

Holy shit
JSON has less features than INI
And there are Redditors defending it for config
No wonder programs become worse

>imagine being brain dead programmer you can't program an ini parser and you have to import json to save and read settings
Dropped

Name one advantage JSON has for settings over INI
>no comments
Faggot

Nesting

Retard
[fuck.fag]
op= gay
[fuck.fag.bitch]
op=slut:faggot:bitch;gay
[fuck.faggot]
you.length=3
you.0=you
you.1=are
you.2=gay
# this is a comment bitch
# let's see gayson do this

>json doesn't have comments
>but check this useless feature no one gives a fuck about

Anybody know how it supports ANSI codes or if it uses something different?

That's just naming sections and values in a way that tries to emulate JSON/XML features but ends up being pointless, fragile and unreadable.

Just post basedjak and pretend like the feature you didn't consider is somehow a deal breaker for you.
Writing an INI parser doesn't make you a 1337 and is just as easy as writing a JSON parser.
That's less pleasant and more error prone than the json equivalent.

>coping so hard
NO COMMENTS

Nigga, nesting is so important, if you have never used that in a settings/config file you have never worked on a project of any complexity.

I prefer XML to JSON, and that has comments. The point is that INI is lacking, not that JSON is perfect.

>wah wah
>import json
>import ini
>lib not found
>wah wah
You used padleft() too?

Use XML then
JSON belongs to the trash along with all programs that use it for settings

I hardly ever use python, what are you on about?

>That's just naming sections
It's equivalent you bitch
I can make a shell script and parse it into a map, dictionary like structure in memory
That's how gay JSON is

>bash terminal
from your picture, it seems like it's WSL
did microsoft really ported BASH to windows?
how does it even work?

Attached: DEVELOPERS.jpg (500x500, 34K)

where my YAML bros at

>devblogs.microsoft.com/commandline/introducing-windows-terminal/
I don't see any bash shell. Are you retarded? Do you know what bash is?

Always bet on XML

shows wsl instances, that's nice.

Attached: 2019-08-25_12-26-20_WindowsTerminal.png (298x292, 9K)

>settings
>ctrl ,
LMAO
MS IS FINISHED

its a terminal emulator you mong

>Jow Forums starts hating json just because microsoft uses it

Attached: 1508953307548.png (464x506, 205K)

>I can make a shell script and parse it into a map, dictionary like structure in memory
The point isn't that you can technically parse it in any way that you want, it's that it shouldn't require any convoluted parsing because the structure the file is written in should already be the actual structure of the data. That results in a lot more readability, compactness, and robustness.

Consider this real example from my job. I have been designing a new frontend which contains panels that can be freely placed in a grid, with separately saved layouts for various modes. The previous GUI used INI files to save these settings, and it was horrible. Every panel had a section with the X/Y coordinates and visibility bool for every possible mode. With like 50 panels and 5 modes, the resulted in an INI file 800 lines long, regardless of how many panels were actually in use. In the new GUI, we switched to XML settings where we could add a block for each mode, and add panels as nested objects within that block if they were visible if that mode. The length of the settings file were typically cut by like 90%, they were far easier to parse, and future modifications to the program like adding/removing panels and modes were super easy.

Nigga, I'm ok with XML.
INI has limits but for a simple config file for a user application is good enough is simple.
I have an issue with JSON.
JSON sucks big time.
JSON was always shit

dhall seems pretty neat, you gentlemen should give it a try.

>JSON sucks big time.
>JSON was always shit.
Why is it shit? You gonna give any reasons or just echo what your thought-provider says?

S in JSON stands for serialisation (where it's actually not completely horrible) not for settings retard.
Fucking pajeet.

>>JSON was always shit
>we've always been at war with Eastasia

>thought-provider
How's the weather in MS online evangelism department of Mumbai?

Continue on with echoing whatever you've heard on Jow Forums you smooth-brain.

Poo in loo faggot
There is no reason to use json for the settings of a shirry terminal or a shitty text editor that requires fucking chrome and javascript to edit text lmao

Why do autists here sperg out so hard over JSON? At least give valid criticism if you feel so strongly about such a fucking pointless topic.

>pointless
I'm the only one who gave a point
>xml: has comments
>ini: has comments
>json: NO COMMENTS
JSON IS SHIT FOR SETTINGS
USE IT FOR SERIALISATION AND STOP BEING GAY INDIAN

Because it will never be as elegant and simple as the tried and true syntax found in .config/i3/config

Nobody even mentioned one of the web-scale text editors. You've yet to actually provide any arguments.
You haven't given any points, JSON allows you to represent related and hierarchical data better is simply unacceptable for anyone with more than a room temperature iq.

And TOML?

>patrician tier
lisp/scheme settings file
>noble tier
turing complete language
>good tier
ini or xml
>shit tier
json

>You haven't given any points
FUCKING RETARD
JSON HAS NO COMMENTS
YOU ARE SO STUPID

json is fine, but it's a dumb choice for a config file, it's not designed for this purpose, so it doesn't support things like comments

>TOML
Goat tier.
In my opinion everything that supports comments is good enough.
You must be a special kind of gay retard to defend json for settings file.
Microsoft managed to find a settings format worse than registry.
>no default values
>no standardized schema
>no self documenting
>no comments
>retard passing settings to eval() opening up the way for new exploits
>json.load(open('settings.json', 'r').read())
>what could possibly go wrong??
Good job MS

I got the gay and sad part but I'm not an oversexualized faggot so I'm not going to get aids.

Attached: 54523424226425.png (500x552, 150K)

That's why I stopped hating the gays.
You didn't ask to be like this.
If you can just be civil well behaving and don't gay up the place you are alright.

Thanks fren. I promise I won't be in your face about it. All I want to do is play music for my own pleasure in peace.

>bash terminal
It's a bash shell or a terminal emulator OP.

There's no such thing as a bash terminal.
Also MS has to upstream any modification to BASH that they ship.

you're not gay
gay doesn't exist
neither does gender

you either have a penis or a vagina. if you have a penis, put it in a vagina. if you have a vagina, put a penis inside it.

why do people have to make things so complicated

>a bourne again shell shell

What if I have both?

then you should have been left out in the snow when you were born like the good old days

>Uptime 0m
0 meter, hasent been running for long :DDD