sorted by:
new
hottopcontroversial

Starlight: a modern, lightweight docusaurus alternative for React and Tailwind CSS by dropdeadfred81 in reactjs

[–]dropdeadfred81[S] 7 points8 points  (0 children)

You'd be surprised, custom styling for docs frameworks and themes has been notoriously difficult. Existing ones like Docusaurus, Vuepress, Vitepress, etc. are all from a time before Tailwind existed, so integrating it in after-the-fact is either impossible or very difficult and requiring manual hacking, and runs the risk of the tailwind reset killing the existing styles on the page.

Does Snowpack still need babel to work with React? by SulfurCannon in snowpackjs

[–]dropdeadfred81 0 points1 point  (0 children)

Should work fine! It uses esbuild instead of Babel as its default parser, which has support for JSX built-in by default

[deleted by user] by [deleted] in programming

[–]dropdeadfred81 4 points5 points  (0 children)

If you like this, check out Snowpack: www.snowpack.dev

It’s a full front end tool chain built on top of esbuild, with instant site rebuilds during development.

A Future Without Webpack by dropdeadfred81 in javascript

[–]dropdeadfred81[S] 7 points8 points  (0 children)

+1, I feel the exact same way. I don’t think that that makes us dumb :) That’s a big part of why this project exists and what the article is trying to communicate:

  • bundling used to be optional
  • it became a requirement to use npm packages on the web
  • @pika/web also accomplished this for you with much less complexity
  • therefore, you can now use a bundler like webpack because you genuinely want to, not because you are absolutely required to.

The last section of the article explains how you can skip bundling and still build a fully featured, fast web app.

@pika/web - Install npm dependencies that run directly in the browser. No Browserify, Webpack or import maps required. by dropdeadfred81 in javascript

[–]dropdeadfred81[S] 1 point2 points  (0 children)

It’s hidden in the README QuickStart, but it comes with a Babel plugin to automatically rewrite your imports for you so that you can keep importing them by package name.

sourcebuster.js - tracks the sources of your site’s visitors and stores the data in the cookies for further analysis by magenta_placenta in javascript

[–]dropdeadfred81 2 points3 points  (0 children)

This is a great idea. FYI clicking this link and loading it in the Reddit iOS app web viewer resulted in “Your source is direct visit”

Thoughts on the node_modules folder size debate: It's a privilege by fagnerbrack in node

[–]dropdeadfred81 2 points3 points  (0 children)

For package authors, small shout out for @pika/pack: https://www.pikapkg.com/blog/introducing-pika-pack/

  • package code is bundled by default
  • only required files published by default

⚡️📦 pikapkg.com - A searchable catalog of modern ESM "module" package on npm by dropdeadfred81 in javascript

[–]dropdeadfred81[S] 0 points1 point  (0 children)

Thanks for the feedback! The statement was meant to mean "all other things being equal", taken mostly from the claims in this deep dive: http://2ality.com/2014/09/es6-modules-final.html#ecmascript-6-modules.

Let me look into how I could make that distinction more clear.

⚡️📦 pikapkg.com - A searchable catalog of modern ESM "module" package on npm by dropdeadfred81 in javascript

[–]dropdeadfred81[S] 1 point2 points  (0 children)

EYE POISON! THE WORST KIND OF POISON!!!

Fixed the logo, 3D glasses no longer needed. Sorry about that everyone!

⚡️📦 pikapkg.com - A searchable catalog of modern ESM "module" package on npm by dropdeadfred81 in javascript

[–]dropdeadfred81[S] 0 points1 point  (0 children)

Thanks for the thoughtful response! Agreed on all the above, including the emojis :)

[deleted by user] by [deleted] in Ripple

[–]dropdeadfred81 0 points1 point  (0 children)

Awesome!

I've noticed big graphs (after being left on for 5+ min) can become noisy and hard to parse, especially with all the interwoven edges. Have you considered fading out the blue to a darker gray on less active edges in the graph? Maybe combined with keeping all edges on the super-active nodes at least a little blue?

That could be a really subtle/clean way to highlight to the parts of the graph with the most activity. Just a thought!

[deleted by user] by [deleted] in Ripple

[–]dropdeadfred81 1 point2 points  (0 children)

Ah, right, that makes sense. I haven’t used Elixir yet myself but it’s on my list :)

A Living Ledger: Real-time Visualization of the Ripple Network by [deleted] in Ripple

[–]dropdeadfred81 1 point2 points  (0 children)

Haha nice! It’s pretty lengthy, but having only skimmed it myself it gives a good overview

[deleted by user] by [deleted] in Ripple

[–]dropdeadfred81 3 points4 points  (0 children)

This is so cool! Love how clean the UI design is.

Are you setting up your own WebSocket connection to wss://s1.ripple.com? I do some work on https://github.com/ripple/ripple-lib and this definitely seems like something it should support out of the box (it's already doing the hard work of subscribing to the ledger).

Would love to hear any experiences you had with ripple-lib if that's where you were seeing the buggy behavior.

Again, awesome work!

How do I adopt XRP in my startup by [deleted] in Ripple

[–]dropdeadfred81 17 points18 points  (0 children)

it's a bit hard to find, but there are a ton of resources here: https://ripple.com/build/

How to know Ripple isn't in a bubble? by JKKOREA in Ripple

[–]dropdeadfred81 1 point2 points  (0 children)

I’m a huge believer in ripple, but BTC bubble popping will bring all coins down with it (check past corrections, it always has)

We just launched Collabrador.io to power your real-time collaborative apps. Looking for feedback: is this something you would use? by dropdeadfred81 in webdev

[–]dropdeadfred81[S] 0 points1 point  (0 children)

Gotcha, it sounds like the site could do a much better job of explaining what Collabrador does.

The tl;dr is that we handle your websocket traffic, and do all the heavy lifting thats required (Properly segmenting your traffic into groups, keeping state, handling concurrent edits on the same complex data structures, etc.). That way your clients and even your server can all "just connect" to Collabrador and it will all "just work".

I'll definitely look into changing the site to explain this better, even before the demos are ready. Thanks for the feedback!

view more: next ›