In my current project, I met a developer who was really confused that I was using an editor and not an IDE for the development of large business applications. First, I did not really consider his concerns but meanwhile, I understand him.
In this blog post, I want to tell you why I now mainly use WebStorm instead of VS Code for development.
This is a very hot topic and I know this will cause some controversy. In the following article, I talk about my experience using WebStorm in a large Angular application which was mainly developed in VS Code.
“Amazon needs brands. We know that consumers search on brands, and so Amazon will go to pretty drastic lengths to get access to those [products],” says Sucharita Kodali, a Forrester analyst specializing in e-commerce and consumer trends. Since the early 2000s, Amazon’s primary way to acquire well-known brands was to let third-party merchants resell them, Kodali notes. “The brands have noticed, and the brands want to control more of their presence online. And because Amazon is such a big presence in e-commerce, if you want to control your brand presence online, you have to control what it looks like on Amazon.” That inevitably means cutting deals and shutting out what, in Apple’s eyes, are rogue merchants.
A collection of open and indie Mac, iOS, and web apps that help promote the open web. Updated May 20, 2019Submit any new links & issues on this project at Github
Source: Mac Open Web, by Brian Warren
ClickHouse’s performance exceeds comparable column-oriented DBMS currently available on the market. It processes hundreds of millions to more than a billion rows and tens of gigabytes of data per single server per second.
In 1988 Laura and I created a three-stage model of what we called “living process.” We called the three stages Good Thing, Rut, and Transition. As we saw it, Good Thing becomes Rut, Rut becomes Transition, and Transition becomes Good Thing. It’s a continuous circuit.
A Good Thing never leads directly to a Transition, in large part because it has no reason to. A Good Thing wants to remain a Good Thing, and this is precisely why it becomes a Rut. Ruts, on the other hand, want desperately to change into something else.
Transitions can be indistinguishable from Ruts. The only important difference is that new events can occur during Transitions, whereas Ruts, by definition, consist of the same thing happening over and over.
When a scientist makes what is recognized as an important discovery or breakthrough, this is perceived as a Good Thing. But then the discovery or breakthrough inevitably becomes a kind of dogma or Rut. This is followed by a period of Transition until someone makes a new discovery, creating a new Good Thing.
The duration of the stages is not consistent from case to case: a system could be in Good Thing for a long time and then pass through a brief Rut—although the opposite is more likely. Good Things by their nature are fragile.
The model as a whole helps to define what might be called a “healthy” system, a system capable of evolution and renewal. Notably, Ruts are integral to even the “healthiest” system; however systems that tend toward shorter Ruts can be thought of “healthier,” of having better odds of survival.
Encountering these ideas again (I found them in an old journal) made me remember Laura, which in turn made me question the model we created. Is our friendship in an extended Rut? A Transition? I know it’s not a Good Thing. Is there a fourth stage we missed? This is what I suspect, only I don’t know what to call it, nor where it fits with the other stages, nor even if it can thought of as a stage. Instead it seems like something that swallows the stages, or that swallows the thing that moves through stages. What is it?
Addendum 10/10/05: I just turned the page in my old journal and found this entry from the following day:
I’m not sure what Transition is, nor if it’s even necessary. Maybe the model should just go: Good Thing, Rut, Good Thing, Rut. This dualistic model scares me because I think the truth of the matter is closer to Good Thing, Rut Rut Rut Rut Rut Rut Rut Rut Rut, Good Thing, Rut Rut Rut Rut Rut Rut Rut Rut Rut….
But this then reminds me of something else: “The nine shallow, one deep rhythm delights your partner. The vacuum has tremendous effect: she feels empty then full, empty then full. This pause pleases because you constantly refresh her senses with change. When we eat our fill, we want no more. But one delicious taste increases desire. We satisfy then stimulate desire. We create desire then renew satisfaction.” —Mantak Chia, Taoist Secrets of Love
Source: Oblivio > Archives > System
Reposting here so it is not lost.
Ethical.net has compiled a list of resources for “discovering ethical alternatives to stuff”. All kinds of other services and apps that tend to be open source, privacy friendly, not supported by advertising, and decentralized.
XState is a library for creating, interpreting, and executing statecharts. Statecharts are a formalism for modeling stateful, reactive systems. Computer scientist David Harel presented this formalism as an extension to state machines in his 1987 paper Statecharts: A Visual Formalism for Complex Systems
Source: Concepts | XState Docs
On mobile, it used to be hard to build beautiful cross-platform apps. Then React Native came along, giving us a seamless way to build user interfaces and manage state in code, all while doing it cross platform.
On desktop, there is no such tool. You can create a GUI using something like Qt, but for people who are used to the React workflow and JSX, there currently isn’t an alternative.
Some of you might be saying that you could do it in Electron. It’s a good tool, but it brings in a lot of overhead, running a full webbrowser to manage a small GUI, while Proton Native can do the same, using native tools, with a smaller size and with less resource usage.
Proton Native does the same to desktop that React Native did to mobile. Build cross-platform apps for the desktop, all while never leaving the React eco-system. Popular React packages such as Redux still work.