Hacker News

Article URL: https://sign.dropbox.com/products/dropbox-fax

Comments URL: https://news.ycombinator.com/item?id=39897573

Points: 4

# Comments: 0

Article URL: https://devblogs.microsoft.com/oldnewthing/20240401-00/?p=109599

Comments URL: https://news.ycombinator.com/item?id=39897565

Points: 1

# Comments: 0

Article URL: https://www.reuters.com/technology/google-destroy-browsing-data-settle-consumer-privacy-lawsuit-2024-04-01/

Comments URL: https://news.ycombinator.com/item?id=39897561

Points: 2

# Comments: 0

Howdy folks. My name is Ryan. I've been building Joystick for the last three years. A few weeks back, I shipped the RC1 release.

tl;dr Joystick is a full-stack JavaScript framework. It combines a component framework with a batteries-included Node.js back-end into one wholistic system. It also has a built-in testing framework so you can do TDD out of the box. It supports MacOS, Windows, and Linux (please file bug reports on Github so I can get them sorted).

My goal is to get a final 1.0 out by the Fall/Winter. After that, the core APIs will be frozen with only new features being added so you don't have to worry about wasting time on surprise refactors (i.e., I won’t be changing how you build your app—just under the hood performance/security stuff).

---

Joystick has been a ~3 year labor (following ~2 years of research/prototyping). I started work on it because I was using the Meteor JavaScript framework as the foundation for apps I was building with students and for clients as part of my old company, Clever Beagle (before that, I wrote tutorials for Meteor as The Meteor Chef).

When Meteor started to fall out of favor/got sold off, I was looking around for something comparable but nothing took. The next closest option was...Next, but it was missing a lot of what drew me to Meteor. Dissatisfied, I started to ask "could I build my own framework?"

Fast-forward a couple of years and the answer was yes. I initially planned on shipping with support for React, Vue, etc., but I noticed a trend toward their APIs becoming more, not less, complicated (simple on the surface, complex once you get into implementation details). I sketched out a component API akin to React 1.0 (h/t Jordan Walke), adding in some missing features that I constantly had to reinvent the wheel to implement on each app (e.g., URL access, data-fetching, etc). Once I had a working prototype: I didn't look back.

As the idea took shape, I started to think about the idea of building an end-to-end stack for shipping apps with JavaScript (a proper response to Ruby on Rails for JavaScript). There were others that had tried, but again, their APIs were lacking that sweet spot I was looking for.

Once I had a solid back-end to front-end combo, I moved on to deployments. Having been burned relentlessly by deployments in the past (culminating in my K8S cluster being decimated by a forced cluster upgrade at DigitalOcean), I decided to go back to basics and see what old tech was available. I was able to get a working deployment using a combo of HAProxy and systemd scripts (which was and continues to be remarkably stable). Instead of using Docker, I do vanilla bootstrapping on the box and have deployments set up to go out to three providers: DigitalOcean, Vultr, or Linode. That service is called Push [1] and is currently in private beta.

Next in my sights is CSS. I'm technically a UI designer (I only started doing JS development because I was tired of building static mockups) and have wanted to build a CSS framework for years. I love the style of Tailwind but the utility class stuff gives me nightmares (both from a maintenance perspective and the thought of future developers being clueless about how to actually write/maintain CSS). That framework will be called Mod [2] and is dropping this summer. It will be responsive, component-based, and feature a vanilla CSS/JS option as well as components built as Joystick components.

---

That's all for now. Drop questions below (see the FAQ first) and I will answer over the next couple of days. If you want to send something privately (e.g., hate mail), just email business@cheatcode.co.

Ryan

[1] https://cheatcode.co/push [2] https://cheatcode.co/mod

Comments URL: https://news.ycombinator.com/item?id=39896946

Points: 1

# Comments: 0

Article URL: http://soft.vub.ac.be/Publications/2016/vub-soft-tr-16-11.pdf

Comments URL: https://news.ycombinator.com/item?id=39896927

Points: 1

# Comments: 0

Article URL: https://github.com/infiniflow/ragflow

Comments URL: https://news.ycombinator.com/item?id=39896923

Points: 1

# Comments: 0

Article URL: https://fortune.com/asia/2024/04/01/negative-interest-rates-30-year-slump-economists-optimistic-japan-back-data/

Comments URL: https://news.ycombinator.com/item?id=39896889

Points: 1

# Comments: 1

Article URL: https://www.businessinsider.com/ev-shoppers-dont-want-detroits-pickup-trucks-they-want-this-2024-3

Comments URL: https://news.ycombinator.com/item?id=39896880

Points: 1

# Comments: 0

Article URL: https://jamanetwork.com/journals/jamainternalmedicine/article-abstract/2817044

Comments URL: https://news.ycombinator.com/item?id=39896868

Points: 1

# Comments: 0

Article URL: https://www.rfc-editor.org/rfc/rfc9564.html

Comments URL: https://news.ycombinator.com/item?id=39896866

Points: 1

# Comments: 0

Article URL: https://poetryincode.dev/product-engineering-with-ifc

Comments URL: https://news.ycombinator.com/item?id=39896846

Points: 1

# Comments: 0

Article URL: https://vtimofeenko.com/posts/practical-nix-flake-anatomy-a-guided-tour-of-flake.nix/

Comments URL: https://news.ycombinator.com/item?id=39896835

Points: 1

# Comments: 0

Article URL: https://blog.frankel.ch/fix-duplicate-api-requests/

Comments URL: https://news.ycombinator.com/item?id=39896810

Points: 1

# Comments: 0

Article URL: https://www.ebay.co.uk/itm/134989142856

Comments URL: https://news.ycombinator.com/item?id=39896792

Points: 1

# Comments: 0

Article URL: https://www.washingtonpost.com/health/2024/04/01/bird-flu-human-case-cow-texas/

Comments URL: https://news.ycombinator.com/item?id=39896787

Points: 1

# Comments: 1

Article URL: https://github.com/Zejun-Yang/AniPortrait

Comments URL: https://news.ycombinator.com/item?id=39896776

Points: 1

# Comments: 0

Were we really do shellshocked by the xz backdoor? I didn't see any

Comments URL: https://news.ycombinator.com/item?id=39896773

Points: 2

# Comments: 1

Article URL: https://twitter.com/feross/status/1774153518800404494

Comments URL: https://news.ycombinator.com/item?id=39896745

Points: 8

# Comments: 1

Hi HN,

I work at a 50 engineer company that decided to adopt microservices few years back. Currently we lack standard practices to establish testing quality for the 30 microservices in our platform.

I am trying to learn best practices that will allow us to establish the right tradeoff between speed of deployment and quality.

Eg:

* what tests need to run before change is merged to release branch ? Do you run some integration tests ? Do you run some performance tests ?

* What tooling is used to slow deploy features (canary, experiments, blue / green) etc.

I am looking for some good resources: books, talks, experiences to learn from.

Comments URL: https://news.ycombinator.com/item?id=39896735

Points: 3

# Comments: 0

Article URL: https://www.stoiczone.com/blog/memento-mori-calendar

Comments URL: https://news.ycombinator.com/item?id=39896712

Points: 1

# Comments: 0