harunurhan

I was curious about this too, and I found https://echarts.apache.org/en/theme-builder.html

I guess "online retailer" example could be extended to many of the companies that are creating consumer products.

it works really well if all you are drawing is an eclipse ¯\_(ツ)_/¯. Could be a bug in the client or your implementation of $1.

I don't think it was particularly good or bad, when I was there. I don't drink beer none of my friends ever said "this beer is great" or "this beer sucks".

Like any user input, you do runtime type-checking and validation. TypeScript is especially great for that because it has type narrowing [0].

[0] - https://www.typescriptlang.org/docs/handbook/2/narrowing.htm...

The cost isn't the only reason

- CERN started planning its computing grid before AWS was launched.

- It's pretty complicated (politics, mission, vision) for CERN to use external proprietary software/hardware for its main functions (they have even started to MS Office like products.)

- [cost] CERN is quite different than a small team researchers doing few years research. the scale is enormous and very long lived, like for decades continue

- and more...

HPC and scientific computing aside, I would have loved to be able to use AWS when I worked there, internal infra for running web apps and services wasn't nearly good & reliable, neither had a wide catalog of services offered.

I think the trick is cutting down animations

> One more thing I've never seen before in a framework's documentation: Patterns

I really appreciate this! btw some DS have that too

https://ant.design/docs/spec/overview

https://carbondesignsystem.com/patterns/notification-pattern...

> the ones that didn’t matter after awhile.

Ideally you have metrics for all flags and their values, so you can easily tell if one becomes redundant and safe to remove entirely after a while.

I've also seen making it a requirement to remove a flag after N days, the feature is completely rolled out.

I bumped into this just yesterday, it's sad that the page ranks very high for "open source ticketing" :(

Not typed support but I find jsonnet [0] pretty useful when you have tons of configuration files.

[0] - https://jsonnet.org/

Have look at this: https://home.cern/news/news/experiments/how-make-your-own-cl...

yeah I didn't know it until i tried to copy-paste to post here :)

OK, seeing "﷽" [1] was unexpected :). For those who does not know, it's very important for muslims and It's all over the Quran

[1] https://github.com/minimaxir/big-list-of-naughty-strings/blo...

I can see it can be, and it actually is useful for many users, but it's not for me, and many others share the same opinion. So having an option not to get the touch bar is important for us.

Well, camera is going to be a lot better than 6s, so as the chip. I think overall it's a good upgrade from 6s, but probably I wouldn't go for it to replace my 8.

It wasn't difficult to know, was it? Gates and some other were already alarming about this, even some documentaries were produced about this.

Not every use case is affected by BREACH attack.

> And especially CERN? These guys have info and tech to end life

I work at CERN, no we do not.

It doesn't sound to me that you really took it seriously and try.

For example for what you said about "JSON objects received from the API" has no type validation, it doesn't unless you define the types for it. You can write interfaces that defines the API responses and use it across whole code base.

Postgres has JSON support. In fact Amazon's documentdb which is alternative to Mongo, is built on top of Postgres AFAIK.

I have worked with polyrepo madness... I do remember doing commits to up to 5 different repos just for a feature. And to roll this feature to prod, few of these repos had to go through release process. On top of everything we couldn't really write tests to ensure if the feature works. The best we could do is write tests on the "user facing" repo and keep fixing and releasing others until those pass.

Well, I am sure many companies doing better than we did, with poly repos though.

Agreed! Also I'd add ant-design [1] and grommet [2] (it is not very active although it works very well)

[1] https://github.com/ant-design/ant-design [2] https://github.com/grommet/grommet

Here's an interesting and relevant project, scoap3. It tries to convert high quality journals to open access with an interesting model.

[1] https://scoap3.org/

Disclosure: I work at the same section as scoap3 team, at CERN.

Interesting project, but I'd stick with idx[0] since I have transpilation setup most of the time anyway.

Also some of you could be interested in optional.js[1], it's Java's Optional for js, makes it arguably more pleasant to deal with null values, no help for chaining though!

[0] https://github.com/facebookincubator/idx [1] https://github.com/JasonStorey/Optional.js

Maybe not the weirdest but;

I was building the client library (wrapper) of an old external third party service we were running, for the our new system (re-write).

By the way, this old third party supposedly has REST interface which was added later, when REST was getting popular. So I needed to get all ABCs but couldn't figure out how because there wasn't any `GET /abc` for ABC but `GET /abc/<id> on the docs. So I just checked how it was done in legacy code.

Then I found a for loop 0 to 100 which was doing 100 `GET /abc/<index>`. It was working because ids were incremental and there were only less than 50 ABC records. Unfortunately there was no caching or `break;` after `404`. :(

Although I like TypeScript as a language, and use Node.js, also really appreciate sharing code such as (data types/interfaces etc.) btw frontend and backend, I think call stack is much worse on the side, especially when you start using frameworks. At least here you get a huge but relevant stack, you can find your business logic, but Node.js it's not rare to get irrelevant unhelpful stack traces which you can't figure out even if you dig in.

In those countries which lack gender equality, in many cases people do not choose STEM because it's really difficult to find a job otherwise.

I have, but by using ngc in my gulp build task (had to use gulp for the reason below), unfortunately couldn't make it incremental at that time, so it takes several seconds to re-build when the source is changed.

There is actually another problem when you want to develop reusable UI component library project is that you have to inline style files and template file into ts component.

I am glad that this approach works for you but I am not brave enough to use a new library without a single test.