For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
dev.to staff -
Vitalii Sevastianov -
Andy Larkin -
Michael Tharrington -
Top comments (62)
Funny how this post got in right when I published my TenserFlow.js post. I've been so excited about having ability to play with machine learning algorithms right into browser that one day my daughter had to remind me she had heard it 4 times from me so far ๐๐๐
Classic ๐
Yaser, so itโs okay and normal that I talk to my newborn baby about TypeScript features while Iโm rocking her to sleep?
Completely, you could even make a song out of it ๐
Sleep, little one,
type systems can be fun!
You'll catch the bugs in time you write
the code so you can sleep at night,
sleep, little one.
This may sound lame, but server-side rendering. I initially didn't jump on the SPA (Single Page App) hype train because it felt wrong to hide content behind JavaScript, making SEO difficult. When I learned that React could actually spit out HTML on the server first, I got super excited to learn it. I'm super excited at how easy it is today too with Gatsby and Next.js.
I wrote about SSR on here actually.
The benefits and origins of Server Side Rendering
Sunny Singh ใป 5 min read
When SSD become available
Oh yeah, that's a good one. I remember where I was when I first found out about SSDs ๐
Thats pretty much uncover how old we are :D
SSD had already existed for a long time before I discovered them, but when it clicked for me in that moment I knew it was going to have a big impact on my computing. I also immediately wondered why it wasn't already shipped as the default drive.
These days it seems like it is the default for most devices.
I recall being incredibly excited about React Native. Not just React Native itself, but it felt like the nudge to really see what this React thing was all about in general.
When React first came around, Angular was already a thing, so was KnockoutJS and several other frameworks.
But I didn't think any of them were fleshed out very well. To me, jQuery was still the best way to get things done with JavaScript at the time. React really changed things. Everything that's come since has been heavily influenced by great ideas introduced by React.
(Not that you need a big JS library for every project, vanilla is often the best choice ๐)
The For-loop in my first month of programming. ๐คทโโ๏ธ
Within the last ~6 months? LiveView with Phoenix for being able make a web app feel like it's a single page app without having to write any Javascript. Diffs of your server rendered templates get pushed over a websocket channel when things change but the initial render happens without Javascript, so you get SEO perks with no extra work.
Within the last ~5 years? Docker to be able to set up a web app and all of its dependencies on any major OS without having to mess around with version managers and service specific installation steps.
Phoenix LiveView is super interesting (though the idea behind is not new, it's a lot less expensive now) and I think it can't be easily replicated within languages that don't have "fearless concurrency" like Elixir :)
Yeah, I used Turbolinks for a long time in Rails. It's not quite the same, but LiveView seems like the next natural stage of progression towards creating responsive web apps.
Although in the project I'm working on now, I'm using both Turbolinks and plan to use LiveView together. Turbolinks still has its place for ensuring the head of your page doesn't get resent for each page view, and LiveView steps in for manipulating pieces of the DOM without changing the page (although push state is coming in a future LiveView release which makes things quite interesting).
Thanks for the details! I'm glad there's no single way to create a web app. Going all in with a SPA is not the only option to have a fast website :D
Hmmm.
I've never been excited about new technology. I've been very excited about 'old' technology though.
dcI distrust new technology - usually old ideas reimplemented badly. The craving for the new is particularly awful in the JavaScript space. At least with old tech you know it's going to work.
.NET Core! My original training was in C#, and I love the >.NET ecosystem. However, a huge down side was this it was Windows only.
Now with Core, its cross platform. Visual Studio even runs on Mac now.
Earlier it was React Hooks, thanks to hooks that the amount of simplicity is amazing now.
I'm also excited about TurboModules in react-native. It is going to change how react-native works forever. Imagine hybrid native app without the need of going through the bridge. It's going to be epic.
Docker. Just getting into it this year but so far it's GREAT.
When I first had a play with Electron, giving me the ability to built full desktop applications in React or any other JS front-end I want. I went on a stream of twitter gushing about it.
No more writing Windows apps in WPF, consistent and easy styling across desktop and web, reusable front-end code between platforms, and I could go on.
When I recently saw Flutter. I like it much more than any other similar framework. I know itโs Google and theyโll prolly can it next month but it is so cool. Using a Mac I can either use VSCode or Android Studio. I actually like Android Studio a lot and prefer that over VSCode. The emulators work great. The only issue I have is that it nests so much it gets hard to read. That is probably just me though.
This has to be Hashcat. Getting it installed properly, setting it up, reading about it, making my script, running valid script, and actually cracking a hash. I think I was so excited that I ran away from my computer and was jumping and did not go back to finish CTF from being so overjoyed by running Hashcat. I think it took me a while to actually return to that machine - days. I was just powerfully in happiness and did not want it to end. And also a bit intimidated by how much happiness it gave to execute this at all. Then I bought a slew of books on Amazon around cracking and nmap and netcat. :)
Well you can probably tell how excited I am about Dependabot by the expletive in my title for this recent article: dev.to/cubiclebuddha/omfg-dependab...
Also, when I first found TypeScript I was so incredibly happy that I could have all of the dynamic object building nature of JS and still get solidly good IntelliSense. Iโve become a bit obsessive about TypeScript since then haha.
GatsbyJS,
.. they succeed in implementing that PRPL pattern as an artist.
GraphQL seems to be a show stopper at first look, but really useful after learning the basics.
It's amazing how much boilerplate work Gatsby abstracts away, how many tools it offers, and the sheer love and effort the community puts in.
Gridsome also, looks promising. It's the Vue.js cousin of GatsbyJS.