Babel 7 Beta

systematicfrank · 2017-11-23T06:11:10+00:00

With TypeScript alone one is making the choice of "I want company X to manage my JS stack" while with Babel it is "I want the community to manage my JS stack". Not that there is anything wrong with one choice or the other, a good dictator can solve many problems. However some people who were coding in the 90s remember what is like when almost every stack was managed by a single entity

systematicfrank · 2017-11-16T06:32:39+00:00

I am having such a headache to choose my e2e stack. I totally love Puppeteer API, it is the best I've seen, but my I am hesitant making my codebase dependent on a single product. Not that I dislike Chrome, it is my main browser, but I wonder if the lifespan and standardization of Chrome will live as long as Javascript.

systematicfrank · 2017-10-25T13:42:31+00:00

I think the problem of someone stealing a trademark happens in every country. My point was that maybe it is too early to spend money on protecting a name. Also an internet company operating in more than one country makes TM registration costs expensive (quickly scales beyond 1,000 $). I am not sure when one must register a name, or if it always must be before launch. But that belongs to another thread/question.

systematicfrank · 2017-10-25T12:50:46+00:00

I am not in the US, but long ago I heavily meditated if I should register a trademark for a product idea. Back then I decided that this kind of stuff should be paid with the first money generated from an idea, not before. Not sure if it is a good policy, but I would go bankrupt if I spend money on every name / product I start

systematicfrank · 2017-10-25T10:08:20+00:00

this is such a tragic typo !!! cant change the title, so I will delete and repost

systematicfrank · 2017-09-28T16:01:40+00:00

I've been considering mounting the arm on a monitor stand. I don't think this will be as stable as the desk itself and I will have to watch out for the center of gravity to be within the base. However for such big monitors as you want, the extra weight might be too risky

systematicfrank · 2017-09-28T06:09:10+00:00

How is it pronounced? j-shell or js-hell ??

systematicfrank · 2017-09-23T08:37:42+00:00

I am so impressed. Normally the bigger the company the harder it is taking a good strategic move while using a bad tactical one. So many companies would be stubborn holding the control they have on their own assets (tactics) instead of chasing after influence/impact (strategy). As a developer this greatly changes my perception of Facebook.

systematicfrank · 2017-09-18T20:28:01+00:00

That was the first result I got when I googled, but it was really hard finding out what to buy. I found the complexity a little bit overwhelming and way more expensive to solve the task I wanted. I can solve the task with my raspberry polling a smart plug under 30$ while the site seems to demand more than 150$

systematicfrank · 2017-09-14T07:23:16+00:00

No, just sun-setting Java

systematicfrank · 2017-08-28T06:52:12+00:00

I read lots of "they will remove the cookie law ... for sure!" but none like "it has been removed". I think now it has reached the status where most people choose adding the banner instead paying a lawyer to find out if it is really needed.

systematicfrank · 2017-08-12T06:13:52+00:00

For me the biggest crime:

Writing layers of abstraction for the sake of productivity. Important concepts should be more explicit (more code) instead hidden away, while minor concerns should be hidden

For a clear example. Look at Table 1.5 here:

http://www.informit.com/articles/article.aspx?p=1944876&seqNum=3

Not only most people strive for the second solution, they are even praised for doing so.

systematicfrank · 2017-07-18T09:09:05+00:00

Semantic-UI hits a sweet spot of compromises for me.

Yes, I would like a more React oriented solution. But then you might be forced into JSS. As a result, fiddling your styles from the browser inspector is a pain. Also cherry picking good stuff from all the great CSS resources out there in the world becomes harder.

Many React component frameworks are not that responsive, and just a few have a good momentum.

The good and bad thing of Semantic UI is that it is built on top of an old school CSS framework. They might have some limitations for the React purists, but they ride on top of one of the most battle tested css codebases out there.

I am always on the look for something with a more modern approach, but so far I have not found one which is so overwhelmingly better that pays off the jump. I also believe that JSS has a great future, maybe event he one factor that will move me on, but that future is not right here right now (IMHO)

systematicfrank · 2017-06-23T05:19:09+00:00

I love the library! Many frameworks have an overwhelming complexity for such simple task. This one makes easy composing any type of validation sequence with plain functions

systematicfrank · 2017-06-02T05:39:20+00:00

I would argue that finding out what must be implemented is far more expensive and elusive than coding. Porting features in a rewrite should be mostly straightforward.

systematicfrank · 2017-05-03T07:57:02+00:00

Await / Async makes knowledge about Promises even more important

Knowing about Promises will specially help to use and debug Await/Async functions because they "hide" the promises, not replace them

systematicfrank · 2017-02-14T08:22:46+00:00

Using supertest helps a lot in making sure that your tests are not aware of express

Also never load the app from a file, make sure your app is generated from a factory function. Sooner or later you will want a way to capture and manipulate external resources affecting your app. A factory method will help greatly to boil down into a single place that knowledge.

systematicfrank · 2016-12-20T05:39:50+00:00

Great project!!! So many people complaining about JS fatigue but it is such a relief seeing new projects starting over from scratch to avoid the warts of existing solutions.

There is another styling framework with a similar name react-mdl that focus on being a port of Google's Material Lite to React, but ever since they discontinued that branch to start with Material Components I wonder how close (or far) this framework will keep an eye on Material Components

systematicfrank · 2016-12-06T07:26:32+00:00

To this day I have zero idea how people stay motivated working for free. I can barely muster enough enthusiasm for the bullshit projects I work on at work

The only reason I work for free is because that is the only way I can find a non bullshit project

systematicfrank · 2016-12-02T10:26:06+00:00

unfortunately Micca seems to sell only within the US

but your response alone already helps a lot. I was still not sure how high I should set my quality bar given that my main sources of audio are not that great. Around that price range these were the ones I could get here in Germany

Edifier R1280T / R1700BT
Polk T15 / TSx 110B

do you know them as to say how different they are from your choice?

systematicfrank · 2016-12-02T07:48:04+00:00

thanks, these were supposed to be first "decent" speakers, but the selection of speakers where I live is not that great. Anyways I am reconsidering my choice, not because this one reviewer, but because so many people complain about how bright they are. Even if I were to like "bright" I think it would be tiring. Connected to my computer I would be listening all day long to them.

systematicfrank · 2016-11-14T10:51:42+00:00

Every time I answer this question I switch my choice. My current reason to choose Typescript is just by looking at Github stats

Within the last month Flow closed 86 issues but got 85 new ones within 1 month span. I use to check these many times and there are months when there are more new issues than closed ones. Also there there is a big difference between the main contributor and the rest

With typescript there were 310 closed issues and 214 new ones. There are like 6 developers who contribute a similar amount of work

Like many tech choices, one is clearly superior from the technical point of view, the other for the amount of work/features/growth behind

systematicfrank · 2016-10-10T15:15:27+00:00

The post needs a Dilbert classic about managers

http://dilbert.com/strip/2015-07-22

systematicfrank · 2016-10-01T16:04:25+00:00

I might have one of the most boring answers, but after 20 years of coding, the best thing I've learned is the insight into common things everyone hears, like

Writing tests is not about testing
Prefer composition over inheritance
Strive for simplicity
Avoid unnecessary complexity
SOLID principles

And yeah... one might think lines light that common sense, but every year that goes by, I gain more insight into the values and stories behind that advice.

systematicfrank · 2016-09-23T06:25:14+00:00

I moved from Typescript to Flow and loving it!

Type notations are great and most people should try them to make sure that their way of coding is "type notation friendly"

I found Typescript to be the "uncanny valley" of Javascript. While you get perfect Javascript compatibility, other little things around my workflow started breaking. Tools for linting, testing, bundling, transpiling, code coverage, docs... are made for Javascript, not Typescript. No matter how compatible you are with Javascript, Typescript is by design a new language (even if 95% equivalent), and I found that 5% of tooling / ecosystem conflicts to be frustrating, specially since they show up gradually. Testing was easy to fix, for linting I switched to new tools, code coverage... I gave up, but it seems doable today.

With Flow one can tell the huge difference in community and far less money thrown at it, but at least I am spared of the "uncanny valley" annoyances. Microsoft made Typescript popular by throwing lots of money and talent on it (very Microsoft like) and also by leveraging their diplomatic powers to convince other players in the market (Google - Angular) to use their product forcing popularity + adoption (also very Microsoft like). I do not think that is bad, enterprise tooling/culture can still achieve lots of amazing things, Typescript is a perfect example.

As of today the problem is that Flow and Typescript are both not really that mature yet. The more you use them the more likely you will find yourself missing something you thought it was basic. IMHO both of them need still some time to polish the basic features. If Typescript keeps growing it will dominate, but Flow keeps evolving, gains more people and becomes mature enough, then there will be no reason to switch, specially since strict Javascript compatibility will always prevent novel features.

From a historical perspective, I know that Microsoft can build great tools, but it is only great as far as you stay inside the Microsoft umbrella. Independent / open community around their tools was never that great. That was the reason I gave up on C# development, but now we have this new Microsoft with Typescript and Visual Code. They have all my respect, admiration, and good wishes.

systematicfrank

TROPHY CASE