mbel

From the article:

> Memory consumption only changed slightly, with a median of 1.7% decrease of V8’s heap size for loading a representative set of websites.

What makes you believe is should be anything significant? After all the JIT-compiled code cannot be that large.

I guess REST became catch phrase for all JSON over HTTP protocols.

And somehow it's more snappy and responsive than some of the pages that are done in HTML today, amazing.

Being alive and fertile does not imply that you will reproduce. There are other genetic factors that may lower chances of reproducing, like having any kind of flaw that makes given specimen "unattractive" for other specimens.

From the post:

> The fountain is required for wishes. The wall is required to be able to offset the random state without advancing the game state – every time the character attempts to walk into a wall, it calls random() without wasting any in-game time. From the fountain, the bot ascends completely on her own.

Instapaper was a sort of nice utility that blocked EU users after May last year. Fortunately there are alternatives, some of them arguably superior (pinboard?).

Let's not forget about immortal RosettaCode: http://www.rosettacode.org/wiki/FizzBuzz

> How do you navigate the Ribbon using a keyboard?

Mostly the same way as you used to do with pull-down menus. Press alt to display tooltips with shortcuts over ribbon buttons. Then you do bunch of alt + [letter] to get the option you want. The underscored letter in traditional pull-down menus in my opinion was similarly non-obvious.

Care to elaborate? I haven't heard about any controversial options coming from Luckey before.

I know it might sound like a wild concept, but let's consider. Is it possible that there are multiple people, who have different opinions, even though they are expressing them on the same forum?

Woah, crazy. Compared to her better known projects, it's hard to believe she was in any way connected to this one.

I would say it's the other way around. You made a tactless and judgemental comment on a sarcastic remark.

This is not even true in C. 0 is a "null pointer literal" when used in pointer context, this does not imply that the actual null pointer has a value of zero.

And obviously dance all the way to fool gait recognition.

> I find it much more useful to make a clear separation between 'preprocessor' and 'compiler'

Yes, I absolutely agree. And to be honest I cannot imagine explaining how preprocessor works without describing it as a separate entity.

It's neither an analogy nor simplification. When he speaks about "compiler state" he means "preprocessor symbol table state". When preprocessor processes a file its state is mutated -- symbols get defined, redefined or undefined.

What you propose as a replacement (an in-memory file) does not provide any insight into why the same file preprocessed twice may end up looking different or why order of included files matter.

Alright, I haven't thought about that. Yes, definitely certification is another option.

Yeah, the only way I can imagine it working is forcing everyone to open source their code. It doesn't sound very realistic.

Console manufacturers have a different revenue model. They get money from games sold for their platform, this allows them to sell hardware with low margin or even at loss.

Apparently there is an eerily relevant XKCD: https://xkcd.com/2030/

Most of them are the same as in Polish. The "prefixes" are called "przyimek" (plural przyimki) in Polish, try googling for that. Here's an example: https://i.pinimg.com/originals/73/ad/c8/73adc83b89ba15c7a79f...

Oh really, what about 'lead' and 'lead'?

> - non static and non namespaced global variable EMOJIS (should be inside the emojize method or at least in the namespace)

The implementation honestly should be put in .cpp file, not a header. Currently it will define both the gigantic statically-initialized map and a function in each module where it's used. Compared to consequences of this lack of unit tests looks like nit-picking.

And yeah, the logic of the function is easy to follow, so it's definitely not modern C++.

Generally sibling comment by IshKebab lists most of the things that were not clear for me. The biggest point, however, is that I wasn't able to get clear picture of what is considered here to be the "documentation". I get what file format is generated, but I have no idea what will be the content and how it will be inferred from my code.

Live? Even offline examples would be great. The description is painfully laconic and it's really hard to guess what exactly is generated. Which is a shame, because the project looks like a rather nice solution to really common problem

Which takes approximately the same amount of time as clicking, going to browser and returning back to the tweet.

"Such an intrinsically faint body could be discovered only thanks to the close Earth flyby in October 2017, which created a tremendous opportunity for the first detailed characterization of a minor object of exosolar origin."

https://arxiv.org/ftp/arxiv/papers/1712/1712.00437.pdf

> With a painting you are getting compared to every other painting, with a program you are compared to other programs for the same task.

Usually you are compared to other paintings done with the same technique and/or style. No one is going to compare your impressionist watercolors with abstract geometric acrylic painting. So in a way it's the same. There are categories both in painting and in software development.

It's even better. Start a project for fun in existing field and people will question why did you even start it. Projects X, Y and Z already exist and have features A, B and C which you haven't implemented yet, how dare you?

The flow in the example is simple: click -> wait -> process result; but it's still there. Notice that instructions are executed in the order they are defined, that is enough to make it imperative.