I believe keeping an eye on trends is essential, tho it doesn’t mean we should jump on the hype-train each time we see new technology go viral.
Personally, I like where Serverless, NextJS and Atomic CSS is going.
Could be worth to keep an eye on Deno and WASM as well.
What dev tech do you believe holds the most future potential?
Top comments (37)
Rust on many dimensions:
Pretty much anywhere Rust can be used, it will be used.
Regarding the web, I have a slight hope that React's implementation will eventually crawl up to the standard in some way. It would be a nice crown to these past years.
If I have to pick a whole lang, I would go with Rust, too 😉
Learning JS superset - TypeScript could be handy, as well. 😉
Well, it's 2020, TypeScript is not the future anymore, its the now 😅
Same as I said with React, if typing could make it to ECMAScript at some point... but perhaps that's even harder.
What is happening with crypto? And how can I get in on it ? Do I have to care about making money?
I guess you understood cryptocurrency, but rather, I meant (and now fixed in the comment) Cryptography.
My questions still stand though
I would like to bring the real state-of-the-art sound effect middleware onto Web Browser as long as WASM can prevent reverse-engineering. All my high-performance sound processors are written in C/C++.
I used to develop for desktop and android platform. Right now only for SoC/FPGA platforms, mainly develop for audio hobbyists in Japan.
Platform / Application
Sound Processors
... and more
Trying to prevent reverse-engineering is almost always the wrong approach, and usually futile. Given that there are a lot of successful organizations that are producing open-source software, I think just having closed source is enough for most people.
The only real way to prevent reverse engineering is with CPU-level encryption. The last time I looked into this, all the encrypted CPUs were still PowerPC-based, since that architecture is open and royalty-free. Although with SGX extensions and support for full memory encryption, there is a bit more support for encrypted data-in-use support on modern x86 processors in the pipeline, at least.
If it's really something you're worried about, the best solution is to handle all the processing at your end -- i.e. "in the cloud" -- where you control access, and keep all your proprietary work that you want to protect on that side of the system. Of course, that comes with performance considerations.
My creation has been successfully protected in an embedded platform. For year's never have an issue of reverse-engineering. Everything is highly encrypted. I just don't trust any platform except embedded. I've used to develop Android apps based on the same library from the embedded application. People easy to reverse-engineer the app but failed to extract the library for porting use in their custom mods. The libs are also encrypted.
This just means they weren't motivated enough to do it. It has to be exposed to the CPU and quite probably memory to be executed, which means unless those are encrypted and protected, someone with the motivation can just dump the assembly instructions from there.
Trust me. The stuff we were trying to protect was a lot bigger deal than just somebody's proprietary algorithms. Some people are very motivated to reverse engineer certain types of application, even if they have no interest in actually stealing or executing the code.
Most people aren't motivated to steal your code. If they just want to sell it, they'll figure out how to bypass your licensing system and sell forged licenses. They might even wrap it in a facade to look like their own application to less savvy users. If they want to compete with you legitimately, they're better off going cleanroom development to avoid running afoul of your intellectual property rights. At worst, it sounds like you were dealing with people with their own internal interests or small-time/casual pirates with no plans to profit from it.
True. It just a matter of time.
I think I need to know more about this. Big audio fan.
Same here, count me as a fan of DAWs, VSTs and mixing and mastering plugins 🎵🎹
WASM! I hope engines go away from browsers and the browser of the future is just a WASM Runtime where we run compiled webapps, maybe we can abstract this way almost everything out of the browser even HTML/CSS, you may be asking yourself how would search engines index my site? Easy just make manifest.json a standard in the web it could replace everything the head tag did, it can hold app title, icons, links to seo APIs where search engines can index.
I seen people shove entire JavaScript interpreters into w a s m. Something like that? Where you could have a single JavaScript implementation to Target across all browsers for all users
Yes!
I want to give a shout out here to the AWS Graviton2 instance types and more specifically how arm processor architecture will make a big impact: more efficient and using less power, great performance and lower costs means that I think you are going to see an explosion in interest and solutions move to arm based architecture. [ I do work for AWS btw, but I have been a fan of arm since the very first Raspberry Pi ]
I see a difference between what trends and what advances the industry.
For the latter, I have seen a lot of value from functional MVU (examples: redux-loop, F# Elmish, Elm). The human memory footprint of MVU is small compared to frameworks and it is highly testable. It does require you to learn new patterns of thinking to solve problems, which I think is why it doesn't trend.
I would definitely keep an eye on Deno and Flutter.
+1 for flutter
while I've seen nothing but praise for deno, I don't think it will be that much popular. Node is too widespread to be taken over by a similar ecosystem. Now, one way it could go to the top is - through WASM.
Remake.
It's an open source framework that lets you build full-stack web apps with just HTML, CSS, and some basic knowledge of JSON.
I'm working on it because I think everyone (not just programmers) should be able to build web apps.
I saw this before, it does have potential.
RedwoodJS
I'm in love with state machine based architectures, so il be watching this.
Purescript & haskell is where it's at :D
Functional programming in general.
It's actually really old, but we're seeing a big push in its use already with the introduction of lambdas to most languages. Considering that even OO language experts were pushing for things like immutability and controlling/avoiding side effects well before functional programming features became popular, I think we're going to start realizing the advantages for things like high parallelism more broadly. I predict this is going to harm the market share of languages like Java that chose a class-first approach instead of an approach focused on modules and languages with natively first-class functions.
Along those same lines, more use of true generic programming -- i.e. "duck typing" and template-driven generics. Again, I see Java being left behind, because of its decision to make its generics erasure-based and not to support its raw types in generics.
Java could solve both of these problems by releasing a non-backwards-compatible version that restructures some of the core language and updates its already well-made memory model and JVM to do away with the legacy support.
I am looking forward to see whether Kotlin manage to replace a big chunck of Java programming on the JVM like it has already done on Android dev.to/jmfayard/kotlin-is-not-andr...
I think probably no, as Java continues to evolve.
However, Kotlin maintained good backward JVM compatibility, up to at least Java 8. But Java itself does not intend that way.
Kotlin also intended to target JS and native; but it has got a long way to go.
Also, Kotlin scripts couldn't yet keep up with JBang.
I don't know, predictions are hard, especially when they are about the future :)
Getting away from Angular and React via
For me it's simply Web APIs. I expect a larger implementation, notably from Apple on mobile.
Ethereum 2.0
Only if they can communicate how to use it way more clearly. I always get bogged down in the jargon.
There's quite a good lot of whitepapers out there to read up on for that. They also include all their Eth talks on youtube so you can see what direction theyre going to.