marcoms

Not sure what you mean, Nim doesn’t allow tabs so that wouldn’t work

This might have been excused if they didn't also forbid tabs unless you use a hack (https://github.com/nim-lang/Nim/wiki/Whitespace-FAQ#tabs-vs-...), was interested in learning until I found this out

Yes, but I think they are emphasising that only a promise will be returned. Any further type information is not given

The code is also compiled to native code, but it's written declaratively. It's not for everyone, but it's not the same as Electron. Even still you have the option to use the traditional imperative API.

Typescript is great at catching bugs which would trickle down to the end user

They are using the Monaco editor component of VSCode, not forking it

UI themes, and a much more cohesive default theme

Atom: the bloat of an IDE with the features of a text editor. At least there are plugins :/

They try, but there is not really predictable and simple way to select those fonts in CSS. I've had times when Courier was used on Linux because the MS fonts we installed.

I would prefer they just do font-family: monospace

Admiring the optimism but having an untested reimplementation of node would make people a lot less confident in using the project

Doesn't headless mode just mean rendering to a bitmap instead of a window?

As others speculated I meant parentheses around the condition - my mistake, I should have qualified

What's the argument for required brackets around if (conditions) and switch (conditions)? To me they seem redundant.

--

As a side point, I hope switch statements are less like C and more like Rust (Rust happens to have better looking syntax, not just because its Rust):

    match <identifier> {
        <val> => {
            //
        }
    
        ..
    }

C-style always creates confusion on how to indent blocks following case statements

Still does not allow tabs for indentation - same problem as `make` but inverted

*Canonical

Why not fixed-size ints - uint8_t, etc. from stdint.h? I've not been using C for a while, so I wonder what the viewpoints are regarding this.

I mean if anything the syntax should me more specialised as you go into sub-keywords, which makes sense in this industry (e.g. ISO 8601). The problem is that `extern` seems to have been taken from C++ and extern crate is almost tacked on (or that's the impression I get). Comparing with other languages, Rust looks to be the only instance where two keywords are required to simply require a module/library, which sticks out to me.

For me what's quite unnerving about `extern crate` is that the `extern` keyword has another function, that is to declare foreign functions [0]. `extern crate` on the other hand, is not an extension of `extern` but serves a completely different purpose.

0: https://doc.rust-lang.org/book/ffi.html

Gtk3 supports macOS natively

You could use Chrome which bundles Flash. The RPM is linked on the download page

https://www.google.co.uk/chrome/browser/desktop/

You could use ` backticks instead and use both " and ' in strings without worry

Also see ES2015's Array.from()

    Array.from(<NodeList or other iterable>)

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

> <paper-button>

It's nice to see Google finally dogfooding Polymer in their own products

> you cannot do overlay blurring like iOS, for example

this may change in the future - the backdrop-filter CSS property should allow you to do exactly that, and support has already landed in chrome

Be careful that you don't trip up using this rule for everything - its not always correct [0]

[0] http://stackoverflow.com/questions/16260417/the-spiral-rule-...

Though I know very little C++, a lot of the questions were applicable to a C programmer

Looks good - bookmarked! Are you targeting a similar demographic to /r/webdev?

One bug I have encountered is on clicking upvote and unregistered, I am redirected to frontends.COM

I believe (s)he means absolute pixel breakpoints instead of percentages

Except there is no "\"product try\"" in this case.

Exactly. At least make it obvious that the user needs to sign in beforehand.