6 ms·

It uses jQuery extensively. The frontend developer in me wants to make a fork written in typescript using react and redux toolkit to manage keystrokes. Then I r

It uses jQuery extensively. The frontend developer in me wants to make a fork written in typescript using react and redux toolkit to manage keystrokes. Then I realize it is just a fun toy.

sildur 6y ago
You could also throw a java back end while you are at it.
- antupis 6y ago
  Also it is missing MongoDB and Kubertenes cluster.
  - deleted 6y ago
    [deleted]
  - carlhjerpe 6y ago
    What about logging? Elastic is a must in every deployment!
    - 0xFFFE 6y ago
      And we haven't even discussed microservices architecture & CI/CD pipelines. Should we included AI powered monitoring?
      - carlhjerpe 6y ago
        Let's bake in some blockchain while we're rewriting this to run serverless with rust->wasm on cloudflare workers to make it 5G ready!
        t0astbread 6y ago
        We're still locked into a single vendor! Let's make it hybrid-cloud behind a service mesh and add an on-premises OpenFaaS instance.
edhelas 6y ago
But why ?
- 6nf 6y ago
  Art
  - antupis 6y ago
    Actually art would be same but using something like GANs or genetic algorithms something overcomplex would hilarious.
- TeMPOraL 6y ago
  CV padding.
coddle-hark 6y ago
Then you realise this is what a lot of people spend their working lives doing, rewriting frontend code in a different framework for no good reason other than they want to.
- goodevans 6y ago
  *somebody wants to...
- Accacin 6y ago
  Yeah, no native tools ever get written in different languages and frameworks. Or is it only not acceptable when Front End developers do it? Personally I've never known anyone do this for any other reason but educational reasons. When I wanted to learn React, I copied other websites in React. I do similar things when I'm learning Golang, or C, or any other language I'm interested in.
  - coddle-hark 6y ago
    I’m not sure what the go/C equivalent of “Ugh, you’re using jQuery? Time for a rewrite” is. It happens a lot more in frontend land than in the rest of the developer ecosystem.
    - mrmonkeyman 6y ago
      C/C++, WinAPI, anything Java.
    - boogies 6y ago
      “Ugh, you’re using C? Time for a Rust rewrite.”
    - webmaven 6y ago
      > I’m not sure what the go/C equivalent of “Ugh, you’re using jQuery? Time for a rewrite” is. Observed "in the wild": C » C++ C++ » C++ w. STL C++ » C# VB » VB.NET WinForms » WPF » Silverlight » UWP Edited to add: Java EJBs » Java Servlets » Java Spring C++ » Java » C#
kgraves 6y ago
wait what why?
- Biganon 6y ago
  Probably a joke
rouxz 6y ago
Sad state of JS frontend. Overcomplicating things is the first thought that we have now, then we think about the requirements.
- madeofpalk 6y ago
  It really isnt. Poor developers might, but poor developers will over complicate things in any domain.
  - grishka 6y ago
    The problem is, the industry favors overcomplicating developers, because there's more of them, over those who actually have a clue what their code is doing.
- Accacin 6y ago
  Why single out JS? Everything developers do nowadays is overcomplicated. See all the posts from large companies saying they switched to this and that for tenuous at best reasons. Then we get a post later saying they're switching back.
- whywhywhywhy 6y ago
  Complain about JQuery yet this loads in less than 300ms. Struggle to imagine any React/Redux engineer I know getting this on the screen in even 3 seconds let alone sub 1. Depresses me how even 10 second webpage load times are considered acceptable in that toolchain, I know it's capable of better but it clearly needs more work to get there than people are willing to put in.
  - DangitBobby 6y ago
    You and I must be using very different react applications.
    - whywhywhywhy 6y ago
      Please send the react engineers you know my way, I'm begging here.
darkhorse13 6y ago
You have a fully working application where the only major issues can be easily fixed by adding `event.preventDefault()` to the keystroke handlers. Instead, you want to throw all that away and rewrite it with some new tool/framework, inevitably introducing new bugs and issues. Unless this is a joke, the question is why?
- taneq 6y ago
  For the same reason that the original was developed: for fun!
  - tleb_ 6y ago
    You are having fun using a modern stack? Please teach me!
    - vanderZwan 6y ago
      Well, for starters, I guess picking a project topic that is fun helps. You could do a lot worse than a bongo cat meme in that regard
    - taneq 6y ago
      No, but then I didn’t make this.
deepstack 6y ago
or Vue
tambourine_man 6y ago
This industry’s best kept secret is that jQuery is as awesome today as it was 10 years ago. The DOM API is so much nicer than the native one it’s not even funny. And when you are not dealing with thousands of buttons you realize you don’t need a virtual DOM. You may even come to the conclusion that if you have so much state in a single view, maybe your UI sucks. And that beneath all the React hype, there were people doing “components“ and “server side rendering” in PHP, Python, Ruby, Java for decades. But I’m not gonna get grumpy this early in the morning.
- whizzter 6y ago
  While i use React at work for bigger things, I've come to use Vue for almost all my "smaller" hacks since it becomes a win to use almost as soon as you start using inputs. After this it scales pretty well up for anything that is on "one page". Apart from work things the main example would be a that I built a small audio sequencer hacked together with Vue. That project would've been suicidal to do in JQuery but also went far quicker to make than if i would've been messing around with doing everything "properly" in React. (Iirc the entire thing is <1000 loc) My main "issue" right now is if i should just leave it and let it be useful at the current level (perfect for creating small retro-style chip tunes with fixed audio channel tone generator controls). Or to remake it in React to enable more easily supporting stuff like view plugins (to control parameters custom instrument/filter plugins), I.e. in principle making it more "application" like rather than just a small one-page hack.
  - antoineMoPa 6y ago
    Have you tried webcomponents?
    - whizzter 6y ago
      Does it solve data-binding? From what I've understood of WC it's about making developing customized elements saner?
      - 6y ago
Shish2k 6y ago
Why so oldschool? Isn’t the new coolness to rewrite your frontend in Rust compiled to WASM? :P
- baybal2 6y ago
  Yet, it's fast. Browsers will always be optimised for the most common JS functions, which even today are nothing else, but showing very basic jQuery based interactive pages.
deleted 6y ago
[deleted]

It uses jQuery extensively. The frontend developer in me wants to make a fork written in typescript using react and redux toolkit to manage keystrokes. Then I realize it is just a fun toy.

sildur 6y ago

You could also throw a java back end while you are at it.

antupis 6y ago
Also it is missing MongoDB and Kubertenes cluster.
- deleted 6y ago
  [deleted]
- carlhjerpe 6y ago
  What about logging? Elastic is a must in every deployment!
  - 0xFFFE 6y ago
    And we haven't even discussed microservices architecture & CI/CD pipelines. Should we included AI powered monitoring?
    - carlhjerpe 6y ago
      Let's bake in some blockchain while we're rewriting this to run serverless with rust->wasm on cloudflare workers to make it 5G ready!
      - t0astbread 6y ago
        We're still locked into a single vendor! Let's make it hybrid-cloud behind a service mesh and add an on-premises OpenFaaS instance.

edhelas 6y ago

But why ?

6nf 6y ago
Art
- antupis 6y ago
  Actually art would be same but using something like GANs or genetic algorithms something overcomplex would hilarious.
TeMPOraL 6y ago
CV padding.

coddle-hark 6y ago

Then you realise this is what a lot of people spend their working lives doing, rewriting frontend code in a different framework for no good reason other than they want to.

goodevans 6y ago
*somebody wants to...
Accacin 6y ago
Yeah, no native tools ever get written in different languages and frameworks. Or is it only not acceptable when Front End developers do it? Personally I've never known anyone do this for any other reason but educational reasons. When I wanted to learn React, I copied other websites in React. I do similar things when I'm learning Golang, or C, or any other language I'm interested in.
- coddle-hark 6y ago
  I’m not sure what the go/C equivalent of “Ugh, you’re using jQuery? Time for a rewrite” is. It happens a lot more in frontend land than in the rest of the developer ecosystem.
  - mrmonkeyman 6y ago
    C/C++, WinAPI, anything Java.
  - boogies 6y ago
    “Ugh, you’re using C? Time for a Rust rewrite.”
  - webmaven 6y ago
    > I’m not sure what the go/C equivalent of “Ugh, you’re using jQuery? Time for a rewrite” is. Observed "in the wild": C » C++ C++ » C++ w. STL C++ » C# VB » VB.NET WinForms » WPF » Silverlight » UWP Edited to add: Java EJBs » Java Servlets » Java Spring C++ » Java » C#

kgraves 6y ago

wait what why?

Biganon 6y ago
Probably a joke

rouxz 6y ago

Sad state of JS frontend. Overcomplicating things is the first thought that we have now, then we think about the requirements.

madeofpalk 6y ago
It really isnt. Poor developers might, but poor developers will over complicate things in any domain.
- grishka 6y ago
  The problem is, the industry favors overcomplicating developers, because there's more of them, over those who actually have a clue what their code is doing.
Accacin 6y ago
Why single out JS? Everything developers do nowadays is overcomplicated. See all the posts from large companies saying they switched to this and that for tenuous at best reasons. Then we get a post later saying they're switching back.
whywhywhywhy 6y ago
Complain about JQuery yet this loads in less than 300ms. Struggle to imagine any React/Redux engineer I know getting this on the screen in even 3 seconds let alone sub 1. Depresses me how even 10 second webpage load times are considered acceptable in that toolchain, I know it's capable of better but it clearly needs more work to get there than people are willing to put in.
- DangitBobby 6y ago
  You and I must be using very different react applications.
  - whywhywhywhy 6y ago
    Please send the react engineers you know my way, I'm begging here.

darkhorse13 6y ago

You have a fully working application where the only major issues can be easily fixed by adding `event.preventDefault()` to the keystroke handlers. Instead, you want to throw all that away and rewrite it with some new tool/framework, inevitably introducing new bugs and issues. Unless this is a joke, the question is why?

taneq 6y ago
For the same reason that the original was developed: for fun!
- tleb_ 6y ago
  You are having fun using a modern stack? Please teach me!
  - vanderZwan 6y ago
    Well, for starters, I guess picking a project topic that is fun helps. You could do a lot worse than a bongo cat meme in that regard
  - taneq 6y ago
    No, but then I didn’t make this.

deepstack 6y ago

or Vue

tambourine_man 6y ago

This industry’s best kept secret is that jQuery is as awesome today as it was 10 years ago. The DOM API is so much nicer than the native one it’s not even funny. And when you are not dealing with thousands of buttons you realize you don’t need a virtual DOM. You may even come to the conclusion that if you have so much state in a single view, maybe your UI sucks. And that beneath all the React hype, there were people doing “components“ and “server side rendering” in PHP, Python, Ruby, Java for decades. But I’m not gonna get grumpy this early in the morning.

whizzter 6y ago
While i use React at work for bigger things, I've come to use Vue for almost all my "smaller" hacks since it becomes a win to use almost as soon as you start using inputs. After this it scales pretty well up for anything that is on "one page". Apart from work things the main example would be a that I built a small audio sequencer hacked together with Vue. That project would've been suicidal to do in JQuery but also went far quicker to make than if i would've been messing around with doing everything "properly" in React. (Iirc the entire thing is <1000 loc) My main "issue" right now is if i should just leave it and let it be useful at the current level (perfect for creating small retro-style chip tunes with fixed audio channel tone generator controls). Or to remake it in React to enable more easily supporting stuff like view plugins (to control parameters custom instrument/filter plugins), I.e. in principle making it more "application" like rather than just a small one-page hack.
- antoineMoPa 6y ago
  Have you tried webcomponents?
  - whizzter 6y ago
    Does it solve data-binding? From what I've understood of WC it's about making developing customized elements saner?
    - 6y ago

Shish2k 6y ago

Why so oldschool? Isn’t the new coolness to rewrite your frontend in Rust compiled to WASM? :P

baybal2 6y ago
Yet, it's fast. Browsers will always be optimised for the most common JS functions, which even today are nothing else, but showing very basic jQuery based interactive pages.

deleted 6y ago

[deleted]