3 ms·

Sentry had a natural path into cloud services because error monitoring has a server-side component to it. Serious question, what is the path for a linter? Wher

Sentry had a natural path into cloud services because error monitoring has a server-side component to it. Serious question, what is the path for a linter? Where else are people paying for linting as a service?

BiteCode_dev 3y ago
I don't know their plan, so I can't speak for them. What I would do is build an entire ecosystem of that quality that would include a tool to solve the Python distributions problem. Either you help with deployment on the server, and you offer hosting. Or you help with making an installer, and you offer nodes to build installers for multiple OS and upload to multiple app stores, manage updates, cdn, permissions... You can even start small and just help with a service for cross-compiling C extensions and scale from that. Or provide machine learning analysis of the quality of your code and make companies pay for it. Or go full Continuum. They are good enough that they can pick and choose whatever they want, really. When you solve pain, people pay. If readthedoc managed to survive by being a static rst site, astral has a shot provided they keep the business side of things in mind as nicely as they build their user stories.
VWWHFSfQ 3y ago
A lot of companies would pay actual money for some semblance of supply-chain security. Hosted, verified, certified Python dependencies. This is how Red Hat made all their money in Linux. Something like "use our vetted and secure pypi instead of the free-for-all full of typo squaters and package takeovers that the public pypi.org offers." Starting with some nice developer tooling and going from there doesn't seem crazy at all.
- prisonguard 3y ago
  > A lot of companies would pay actual money for some semblance of supply-chain security. After the core-js debacle[0] earlier this year, it was evident that alot of companies actually do not care care about supply-chain security. Those that do will happily roll their own hosted repositories that provide little to no guarantees. [0] https://github.com/zloirock/core-js/blob/master/docs/2023-02-14-so-whats-next.md https://github.com/zloirock/core-js/blob/master/docs/2023-02...
- BiteCode_dev 3y ago
  That's Anaconda's business model.
sangnoir 3y ago
> Serious question, what is the path for a linter? The natural end state is yet another build service.
baq 3y ago
SAST/DAST products cost truckloads of money, so that’s a possible direction. The linter is a tech demo in this case.
- muglug 3y ago
  Some SAST products cost a truckload of money. There's a FOSS SAST product for Python already, though, called Pysa: https://pyre-check.org/docs/pysa-basics/ https://pyre-check.org/docs/pysa-basics/
Aeolun 3y ago
Cloud linting! You send your content hash to the cloud, and it’ll tell you what errors you have.

BiteCode_dev 3y ago

I don't know their plan, so I can't speak for them. What I would do is build an entire ecosystem of that quality that would include a tool to solve the Python distributions problem. Either you help with deployment on the server, and you offer hosting. Or you help with making an installer, and you offer nodes to build installers for multiple OS and upload to multiple app stores, manage updates, cdn, permissions... You can even start small and just help with a service for cross-compiling C extensions and scale from that. Or provide machine learning analysis of the quality of your code and make companies pay for it. Or go full Continuum. They are good enough that they can pick and choose whatever they want, really. When you solve pain, people pay. If readthedoc managed to survive by being a static rst site, astral has a shot provided they keep the business side of things in mind as nicely as they build their user stories.

VWWHFSfQ 3y ago

A lot of companies would pay actual money for some semblance of supply-chain security. Hosted, verified, certified Python dependencies. This is how Red Hat made all their money in Linux. Something like "use our vetted and secure pypi instead of the free-for-all full of typo squaters and package takeovers that the public pypi.org offers." Starting with some nice developer tooling and going from there doesn't seem crazy at all.

prisonguard 3y ago
> A lot of companies would pay actual money for some semblance of supply-chain security. After the core-js debacle[0] earlier this year, it was evident that alot of companies actually do not care care about supply-chain security. Those that do will happily roll their own hosted repositories that provide little to no guarantees. [0] https://github.com/zloirock/core-js/blob/master/docs/2023-02-14-so-whats-next.md https://github.com/zloirock/core-js/blob/master/docs/2023-02...
BiteCode_dev 3y ago
That's Anaconda's business model.

sangnoir 3y ago

> Serious question, what is the path for a linter? The natural end state is yet another build service.

baq 3y ago

SAST/DAST products cost truckloads of money, so that’s a possible direction. The linter is a tech demo in this case.

muglug 3y ago
Some SAST products cost a truckload of money. There's a FOSS SAST product for Python already, though, called Pysa: https://pyre-check.org/docs/pysa-basics/ https://pyre-check.org/docs/pysa-basics/

Aeolun 3y ago

Cloud linting! You send your content hash to the cloud, and it’ll tell you what errors you have.