clon

This timeout issue is indeed baffling. I believe many Go services out there may have set their timeouts to something ridiculous like 3600 or 86400 as a "fix". Hello slow lori.

Another concern is that the lifetime of a PHP app is rather short, measured in milliseconds. This is actually a rather robust approach. Crashes, memory leaks, all sort of weird states are brushed away immediately to be replaced with fresh state for the next request. Apache/nginx is acting as a supervisor and allowing a lot of shit code live out it's days unnoticed.

Contrast that with long-running Golang processes. You won't get away with sloppy code there, raising he bar considerably. Running a Go executable without a monitoring supervisor is sketchy at best.

Absolutely, having a service that just listens on port 80 is so much simpler to reason about. I would also add a much easier development setup, as well as deployment to your list of advantages.

That said, having a Go service just be exposed to the wild wild internet may not be a smart idea. Take a look at this issue [1], it is perfectly clear that Go services (relying on net/http) still need babysitting by a competent reverse proxy. It is a case where Go's mantra about simplicity leads to leaky abstractions and just clearly immature solutions.

Also not talking about TLS certs, WAF and other concerns that also may bring nginx etc on board anyhow.

[1] https://github.com/golang/go/issues/16100

I am not looking forward to using a new improved shell written in JS.

I never knew they had a second, unfinished, airframe ready for assembly.

A close friend's father was one of the persons to return from Gulag. He was one of the few people that buried the rest of the camp, due to him being immune to whatever disease that killed everyone else. Survived, came back and conceived my friend, all thanks to a lucky mutation somewhere.

Much of the "progress" in the USSR was based on slave labour [1]. And it was not limited to just physical labour. Many intellectual feats were also the product of people working in, what essentially amounts to, a prison [2].

[1] https://en.wikipedia.org/wiki/The_Gulag_Archipelago

[2] https://en.wikipedia.org/wiki/Sharashka

I remember the curved white kidney-shaped enamel bowl! After the operation, I joined an adjoining room where a number of other stunned and stupefied children were sitting, each grappling their own little enamel bowl and staring at pieces of their flesh, blood dripping from their nose and mouths.

A tonsillectomy.

I am not from UA, but this video seems to be about right: https://youtu.be/ihBGocSbC-I?t=124

I am in my mid-thirties and I was still operated on without anaesthesia as a child, growing up in a Russian-occupied part of Europe.

I remember being tied to a sort of lazy-chair with heavy belts and getting a giant lollipop afterwards. Everything in-between seems like a blur.

While it sounds brutal, it was actually a better option, and I am thankful to the surgeon for not putting me under. The thinking was, as I understand now from speaking to my parents, that soviet anaesthesia options were rather primitive and dangerous, especially to a child, and the surgeon elected to omit it, making the operation that much more challenging. Thankfully, he was at the top of his game.

Looking at the 'Graphical Abstract' in the excellent link [1] that seesawtron posted, I don't think you did miss anything.

[1] https://bit.ly/3cy0C9u

I cannot stand those long form articles. The headline picked my interest, the lead text is intriguing but the first paragraph that starts to describe a bright, warm morning or the attire or the facial features of a "lead character" immediately takes the wind out of my sails. How can anyone place so little value on their time as to be able afford to consume material that is so sparse in information?

Thanks, this is a fascinating resource!

My logic with the address field is to try to consider what is the purpose of the address in the application.

If it is used for someone to send you a letter in the mail (for example: university admission) then you are better off with a big box where the user can write the magic blob of text that usually gets their mail delivered to the right place, up to instructions to the local postman.

If you need to pull off some analytics, or need to estimate shipping, then just extract the fields that your shipping agent demands: country, zip code etc. Leave all else intact in the "magic blob".

Absolutely! Having 'name_given', 'name_middle', 'name_family' or some nonsense like this is one of the most common mistakes in database (and application) design, usually made by culturally narrow-minded Western developers.

Take names in Myanmar [1] as an example. From Wikipedia:

> Burmese names lack the serial structure of most modern names. The Bamars have no customary patronymic or matronymic system and thus there is no surname at all.

That said, it is hard to push back on a business requirement to sort users A-Z based on family name, just because.

[1] https://en.wikipedia.org/wiki/Burmese_names

PHP-s strtotime() will probably handle them all, even though it will make you cringe a bit.

I never understood why simple integer unix timestamps are not more prevalent in API-s? Or some monotonic count from any reasonable epoch, depending on the context. How many APIs really have to ever return dates predating unix?

I cannot shake the feeling that the inner emblem should be moved down just a tiny bit. Visual subjective balance is not the same as geometric balance. It just looks visually skewed in the vertical dimension.

What a poor result.

Would this explain the apparent sudden collapse of people on the streets in China and Iran? [1]

[1] https://www.snopes.com/fact-check/people-collapsing-coronavi...

By hefty price, did not mean any potentially mishandled quarantine measures. Quarantine is a compromise, a hard one, and I am certainly in no position to form an informed position on this matter.

I meant the human rights violations perpetrated by the regime. This is always the price we seem to have to pay for a "competent crisis handling". I would indeed rather choose a free, but impotent country.

It is ironic that personal freedoms and public health are not often compatible. Doubly important to be aware of what we are being sold.

It is interesting how in times of crisis, people start looking for a heavy handed, authoritative response to the situation. Moderates will be brushed aside as weak and impotent.

I do not disagree with you on the point that China's response has been herculean, but we must not forget that this also comes at a hefty price, one that I am personally not willing to pay.

I was also wondering why they would have me watch someone's dirty keyboard, sunrise and other apparently meaningless motifs.

The scene with the keyboard with crumbs and hairs tells me that they do not respect their own product enough. A good example on how the effort of hundreds of people that contributed to this awesome release is being ... not appreciated.

It has been my observation that tech people tend to place less emphasis on aesthetics or, god forbid, marketing or sales. This functional fixation is unfortunate - many people do engage in emotions, enjoy looking at pleasant things, tend to appreciate harmony and subconsciously associate themselves with things that bear the same values as they believe themselves to possess.

I don't think a lot of people will find a way to associate with this presentation.

A former KDE user, looking to come back.

Thank you, this was an interesting read. TIL.

The cynical among us can view this as an opportunity to invest in honey.

Clearly the bigger problem is that bees are one of a kind pollinators, without them we will probably starve in large numbers. But I wish my grandchildren would have the opportunity to taste real honey - unprocessed, unfiltered, unpasteurized with the amazing texture.

Luckily for us, honey has an almost indefinite shelf life, if stored properly (basically kept in a sealed jar, in a cool dark place). I have tasted honey that was at least 70 years old and despite the weird colour (almost black), it tasted just fine.

This is worrying. I presume they have some scrubbers at least?

Despite all the global warming alarms, the Earth is still a thermally open system. In terms of toxic materials, pollutants and interesting new molecules, Earth is a closed system - they stay here for us to deal with.

Personally, I am more worried by us poisoning ourselves long before we cook ourselves.

> Well, in real code you are likely bubbling up an error in some way for your 404 Not Found and 500 Internal Error handlers to kick in.

Which is essentially GOTO 404

A horrible idea that I see often in clever frameworks disobeying encapsulation and reasonable control flow in favour of magic

As far as I have been able to gather, the MCAS software performed exactly to spec. You may have been drawn to the Boeing straw man narrative "the software was faulty (we can fix it)".

Seems like a passive-aggressive PR scheme to still try to indirectly lay blame on the dead pilots. Despicable.

> This meme has been debunked several months ago but keeps getting repeated along with the more ignorant 'the plane is inherently unstable'.

Yet, there has been no information released, at least publicly, as to the bare airframe flight characteristics (bare as in sans MCAS).

The reasons for the initial inclusion of the MCAS seems like it may have been related to the augmentation of the "touch and feel" of the flight controls, but we simply do not know at this point what were the reasons for the increase of it's operating envelope and authority.

> Please stop spreading thoroughly debunked misinformation.

If you have a source for the debunking, I would appreciate if you could share it. In the meantime, our best bet is to hope for one of the other CAA-s to conduct said bare airframe tests.

I suspect that one must also consider that the Boeing's PR department is busy coloring the narrative in a favourable way.

Source: https://www.faa.gov/news/media/attachments/Final_JATR_Submit...

Recommendation R3.4:

The FAA should review the natural (bare airframe) stalling characteristics of the B737 MAX to determine if unsafe characteristics exist. If unsafe characteristics exist, the design of the speed trim system (STS)/MCAS/elevator feel shift (EFS) should be reviewed for acceptability.

Observation O3.4-A: The original implementation of MCAS was driven primarily by its ability to provide the B737 MAX with FAA-compliant flight characteristics at high speed. An unaugmented design would have been at risk of not meeting 14 CFR part 25 maneuvering characteristics requirements due to aerodynamics.

Observation O3.4-B: Extension of MCAS to the low-speed and 1g environment during the flight program was due to unacceptable stall characteristics with STS only. The possibility of a pitch-up tendency during approach to stall was identified for the flaps-up configuration prior to the implementation of MCAS.

Finding F3.4-A: The acceptability of the natural stalling characteristics of the aircraft should form the basis for the design and certification of augmentation functions such as EFS and STS (including MCAS) that are used in support of meeting 14 CFR part 25, subpart B requirements.

In short, Boeing designed a full-authority flight envelope protection system, just like Airbus has. Except for the fact that Airbus uses a full triplex system (3 ADIRU-s with their own set of sensors), while Boeing went with a single source of data, treating the wetware on the seat as the pseudo duplex channel ("you are the backup", while neglecting to inform them of their role, or their potential physical inability to accomplish this, nor provide accurate force feedback in sims). Now they are trying to sell us a duplex/pseudo-triplex model with the consolation that while the beast still has half a brain (pun intended), it is at least more tame. All this while simply neglecting to tell us, the pilots and the flying public, exactly why it was needed in the first place. See O3.4-B above.

Disclaimer: pilot.

I spent some of my best years bootstrapping a business (trying to avoid the word "startup"), growing steady each year 30-50%. No hockey stick so far, but our customers are happy and the product rocks.

1) It is hard, properly HARD.

2) It does not seem like it is fair to yourself - you might feel like you are not really giving yourself a proper chance, be it capturing the market, hiring the best possible talent etc.

3) It might make you more risk averse, as you are gambling with your baby.

4) On the other hand, it is not the low risk path either, so it sort of conflicts with #3. I mean that there are a lot of risks involved in raising capital at an early stage, but going the tortoise path has other kinds of risks. Also see #2.

5) Your type of market needs to support it, obviously. Low investment product, stable customer base. In our case, the customers are large semi-governmental organizations and in all of history we have lost just 1 established customer. This gives a lot of consolation that you are building a house, one brick at a time.

6) You need a lot of mental stamina - everyone else seems to be doing things more cleverly. Your buddies will move on to work for the big bucks and establish their careers, others might be busy burning through VC money. It will take time.

8) Sometimes an investor will come along and try to offer you their money. But it often turns out as if your are playing a totally different ball game. One thing I learned was to ask not just how many X they expect us to deliver, but straight out ask how many X-s their "family" or whatever expects them to deliver.

But in the end you might have a company that is actually self sustaining, fantastic people around you and customers that appreciate what you are doing to them. I consider myself lucky, though. Feels like all odds were stacked against us.

He did come across as a basically decent person.

He was not ousted for being unable to undo the MBA damage. He was let go for being unable to jedi mind fuck the plane back into the air. This, as far as his employers are concerned, is the measure of his failing.

David Calhoun is the replacement - head of Blackstone private equity. An accountant running an engineering company, what could possibly go wrong.

You can assume that stock price will take the front seat now, if it already had not. The bean counters have yet to internalise the fact that it is am engineering culture failure, stemming from the toxic MacDac merger. This is a further signal that things are going downhill for Boeing.

To be fair, Dennis Muilenburg was at least an engineer, lead the X-32 program (the funny looking bug plane that was runner-up for the JSF). An engineer, possibly at am advanced Peter principle level, but an engineer.

I am thankful for this release. It finally fixed two major issues that had plagued Gitlab for us for a long time:

- The "Rebase" button now actually seems to work reliably with no cases of endless spinning to report in the few tens of button presses so far for me (we merge fast-forward only). Hoping this is not a fluke and will not regress in the future.

- The "Hide whitespace changes" button works again after breaking what feels like some time in 2018.

These 2 sound like really basic functionality, so it also represents the sad state of Gitlab development - a priority on useless fluff on top of regressions in each release, while hundreds of bugs that actually affect users go unaddressed.

This is a good release.

Edit: Their issue tracker [1] actually lists 37.8k issues with 23.9k "open", which represents 63% of all issues ever created. As a project matures and ages, you would expect this metric to start to go down naturally, as you "plateau" on a sustainable level of open issues. If this were my project, I would be freaking out.

[1] https://gitlab.com/gitlab-org/gitlab/issues