codeburst.io

Great discussion - https://codeburst.io/software-estimation-in-the-fractal-dimension-9145…

Yep, sorry I should have included the reference. This post is by the redux-form creator, in which he states why it was a bad idea, and announces its 'spiritual successor': https://codeburst.io/final-form-the-road-to-the-checkered-flag-cd9b75c… > Also, everyone high up in the React community, including both inventors of Redux [1], say that Redux is not the best place to keep form data. Oops. [1] https://github.com/reactjs/redux/issues/1287#issuecomment-175351978

From my notes, these two don't work when followed exactly: https://www.adcisolutions.com/knowledge/how-build-single-page-applicat… https://codeburst.io/full-stack-single-page-application-with-vue-js-an… The first one doesn't build, if I remember correctly, and the second doesn't display anything after about the halfway point. I'm running them on MacOS. I tried a couple of others with similar issues, but didn't save the URLs.

The laws of physics didn't change, it's great but suffers most of the problems of IR communication, namely air diffraction/absorption (severely hurting range) and mostly line of sight communication. Through advanced modulation schemes one can reach gigabit speeds but it's such an extremely short range[1] it's no surprise there seems to be no commercial product. Terahertz signal processing, though, has a much brighter (hah) future ahead, in medical and security imaging[2]. [1] http://www.embednet.com/Giga-IR_General.pdf [2] https://codeburst.io/terahertz-thz-gap-tech-for-speedy-communication-c…

The author wrote a follow up about how he thinks you should build things without using a relational database: https://codeburst.io/doing-without-databases-in-the-21st-century-6e25c… I think he should rename his book Creating IT Disasters

I dunno. I'm a long time reddit user, but I'm done with it. It's really time to just dig into some self hosted shit with a reasonable ingress like Cloudfront or whatever works and just dump this crap. People still say "and my axe" on reddit. We don't need this siloed internet anymore. mTLS is SUPER easy to implement and in my opinion is the future of the internet. I've got some courseware as well as some simple VMs, containers, helm charts, juju charms and I've got a process for building custom distros with GPU support and clusters inside clusters that can federate with enterprise org level OIDC. I'm a bit ahead of the curve I think? I don't know. All this talk about the big guys, we are at a tipping point. It's happening now. That's why they are trying to regulate AI IMO. They understand that we are moments away from being able to bridge all of our own resources in a way that isn't siloed. We can host it all ourselves now. It's fine. The future is going to be weird... but really it's just getting the internet back that got hijacked from us 20ish years ago or whatever. If you want to try yourself, since I can't recommend my gear because I have to finish the rest of the rollout, KubeSail doesn't get enough attention. Easy to set up on any computer you have laying around, but their gizmo is pretty cool too. I think their app store is neat and I could get my grandma hosting her own K8s cluster to the web with this tutorial. https://codeburst.io/ddclient-c9a6ac1d8f81 Throw…

Sure, object-relational impedance mismatch is a problem, but if you're going to throw the baby out with the bathwater, you need to propose alternatives. Luckily for us, this is not the author's only post... The author's followup article advocates instead for building your own in-process persistence system for each application, with no persistent data structure other than a (non-write-ahead) log, even for an application the size and scale of Stack Overflow itself: https://codeburst.io/doing-without-databases-in-the-21st-century-6e25c… I post this only because "name 20 things wrong with this article" might be a good take-home exercise for a student, or as a weeding exercise for recruiting... except that, on the off chance the student/candidate were to fail at said exercise and buy into the content unironically, I would have caused irreparable and irresponsible harm to their learning process, their future businesses, and the safety of their customers' data. Seriously, what we have here is a fundamental misunderstanding of ACID, of the very idea that a computer might crash at an arbitrary point in a program, of the general importance of distributed systems, of safe software deployment, of parallelism, and of the very idea that a schema might evolve over time. It saddens me to know that this type of advice exists and receives a platform.

Hello everyone! Today, we are launching a major release of Reactivesearch (v2). Key highlights: - Compatible with any Elasticsearch index hosted anywhere. - Comes with over 30 pre-built components which are common in building data-driven UIs. - Can be extended to work with your own UI components. (Really handy if already have a designed component and want it to work with Elasticsearch). - We also provide designer templates of all our components, which is helpful for creating pixel-perfect UIs. - Consistent API for web and native mobile apps (Native version of the lib is in alpha today) You can see a post for building an e-commerce UI using Reactivesearch - https://codeburst.io/how-to-build-an-e-commerce-search-ui-with-react-a… A lot of sweat and love has gone into building this, would appreciate any helpful feedback, improvements we can make, or issues you may be seeing. :)

We've several thousands of nodes in our system. Our ops people have witnessed clock skew from seconds to months that are transient. Time is constantly synced via ntpd. You can't trust system clocks in a distributed system to ensure ordering. Some reading: https://codeburst.io/why-shouldnt-you-trust-system-clocks-72a82a41df93

Previous post or links from previous posts I found useful: https://news.ycombinator.com/item?id=26243107 https://codeburst.io/tech-stack-how-i-quickly-developed-and-launched-a…

I collect examples of systems that have helpful error messages. Here's a blog post (not mine) that praises error messages in React [1]. Any other examples? [1] https://codeburst.io/the-true-delight-of-reacts-error-and-warning-mess…

Sure hygienic macro belongs to macro but saner. Mixin is not macro according to D authors. If you dig into Walter's past posts, perhaps you can find better explanations there than mine. You can have macro in any runtime for example Ruby language, and that's the main reason for the maxim "Rails is not Ruby". That's also the reason Ruby is so powerful and to create a similar feat in Java will be close to impossible [2]. But at what cost? That's why Python now is much more popular even though Ruby is much more powerful. You can, however, create Rails clone in D language without all the macro nonsense [3]. [1]Ruby Macros Explained: https://codeburst.io/ruby-macros-18bb67e051c7 [2]Stop Designing Languages. Write Libraries Instead: http://lbstanza.org/purpose_of_programming_languages.html [3]Diamond CMS: https://github.com/DiamondMVC

I'd not come across FlatBuffers before, but they do seem interesting for some use cases, especially when you're highly performance sensitive. https://codeburst.io/json-vs-protocol-buffers-vs-flatbuffers-a4247f8bd…

https://nshipster.com/uuid-udid-unique-identifier/ Not his solution, but just grab the identifierForVendor off UIDevice and ban that. Alternatively: > "Using DeviceCheck API’s, in combination with a server-to-server APIs, developer can set and query two bits of data per device. It will also maintain the user privacy, by not disclosing any user or device information, which is the priority point for every Apple user and most point of concern of every mobile user." https://codeburst.io/unique-identifier-for-the-ios-devices-590bb778290…

You can also upload IPA files to your iPhone using older versions of iTunes that supports sideloading saved (but purchased) IPA files. Apple now offers downloads for these older versions of iTunes, see here: https://support.apple.com/downloads/itunes Apple also makes iTunes 12.6.x available for download, but it's hidden on this page: https://support.apple.com/en-us/HT208079 - this is the last Windows version with IPA management, but there are also other ways to sideload IPA files without needing XCode and a developer signing certificate, e.g. https://codeburst.io/latest-itunes-12-7-removed-the-apps-option-how-to… The question is - how are we supposed to save and archive those IPA files today?

Made a platform for party/drinking games over Zoom. https://ziago.co Games run on Realtime Firebase DB, so players join with a link and everyone is kept updated with game flow and other player actions etc. So far had 10000 people play, and has 9 games and still working on more. The focus for now is on social/turn-based kind of games. Runs on Vue and Firebase. FB helped me to launch it in a month. Wrote about it at https://codeburst.io/how-i-built-a-real-time-games-platform-for-social…

How come you haven't used tagged template literals? These would fit this use case: https://codeburst.io/javascript-es6-tagged-template-literals-a45c26e54…

Read this blog to know more about the use case: https://codeburst.io/how-secure-is-your-environment-file-in-node-js-7c… This is a solution to this tweet https://twitter.com/o_cee/status/892306836199800836?s=20

Not only that, but in the context-switching overhead, the numbers provided are not appropriate to golang - because go's function calling convention assumes fewer registers are saved, thus reducing context switching overhead. From : https://codeburst.io/why-goroutines-are-not-lightweight-threads-7c460c… "In Go, this means only 3 registers i.e. PC, SP and DX (Data Registers) being updated during context switch rather than all registers (e.g. AVX, Floating Point, MMX)" Perhaps a better title would be "Fibers require compiler / language support to be viable"

In javascript you can use an object, and then use destructuring to automatically convert the properties into local variables within the function. Which is super useful and easy to read. getUserMessag({userId:1234, retriveFullMessage:true}) https://codeburst.io/es6-destructuring-the-complete-guide-7f842d08b98f

> Parsers have become so fast that I feel they might even have the opportunity to be faster than a protobuf based solution. Not even close. Event new JSON serializers/deserializers aren't magic. Protobuf is a LOT easier to parse, so it's naturally a LOT faster. First two duck results for "json vs protobuf benchmark": https://auth0.com/blog/beating-json-performance-with-protobuf/ https://codeburst.io/json-vs-protocol-buffers-vs-flatbuffers-a4247f8bd…

This very article ends with '"¿Por qué no los dos?", which means "Why not both?"'. I agree, use both, but don't get carried away with either. If you exclusively use composition you're basically reinventing inheritance anyway, with more steps. But the linked article is reasonable. Less reasonable articles like this one exist, however: https://codeburst.io/inheritance-is-evil-stop-using-it-6c4f1caf5117 These are the articles where someone saw that the "cool kids" don't like/use inheritance, and so adopted the position to try and be "cool". Don't try to be cool, try to understand. Inheritance doesn't say, "Create a complex inheritance tree of interdependent classes". That's the strawman. Remember that.

Interesting read from Dec 2018 [1] about Next.js: SSR throughput of your server is significantly less than CSR throughput. For react in particular, the throughput impact is extremely large. ReactDOMServer.renderToString is a synchronous CPU bound call, which holds the event loop, which means the server will not be able to process any other request till ReactDOMServer.renderToString completes. [...] Using Pre-Rendered CRA addresses both the SEO and performance concerns around using CRA without the complexity that Next.js introduces [1] https://codeburst.io/next-js-ssr-vs-create-react-app-csr-7452f71599f6

Looks like it's addressed here: https://codeburst.io/magic-grid-f8e2221e7cef

If you enjoy writing html without the annoying punctuation, you might also like Pug: https://codeburst.io/getting-started-with-pug-template-engine-e49cfa29…

Having scanned over some of what you link, I would suggest learning a bit about fractal geometry and the possibilities of non-integer dimensions. I suggest this because code and modules probably don't multiply exactly as an area. This will be especially true if you try to go beyond 2D, because the discrepancies between the full R^n space and what software actually does (streak through it in something like a powerlaw distribution) will become worse and worse. (See something like https://physics.stackexchange.com/questions/55269/why-do-fractal-syste… .) See also some ideas in https://codeburst.io/software-estimation-in-the-fractal-dimension-9145… or https://www.quora.com/Engineering-Management/Why-are-software-developm… for more thoughts that head in that direction.

I wrote a tool to automate this (right now it's just JavaScript coverage) here: https://github.com/joelgriffith/navalia. Here's a walk through on the doing so: https://codeburst.io/capturing-unused-application-code-2b7594a9fe06?so…

Honestly, I had no idea that "monkey-patching" was a term, I thought it was something Op just made up :-). I have just looked it up, and it indeed is a term [meaning something](https://en.wikipedia.org/wiki/Monkey_patch). Even meta-magic seem to be a term, but less defined seems like. I don't think we need AST for monkey-patching, but it can be argued that each program can be converted to an AST. Anyway, less important. The "monkey-patching" seem to basically mean anything that changes the runtime somehow. The example in Python on Wikipedia article just changes the value of a global variable. In Lisp we have many, many tools which can change code at runtime, I would even argue that Lisp is all about flexibility and "monkey-patching" since we already write AST and have the entire symbol table and the compiler available to us at runtime. Functions are just objects like any others and we can install any object in the function slot of an symbol, we can wrap it in our own function and install that one, everything is a list and dynamic in some way, so we can add slots to classes and structs if we want etc. For meta-magic I found [this one article](https://betterprogramming.pub/the-magic-of-metaprogramming-732f0300a5c… and [this one](https://codeburst.io/laziness-i-meta-programming-34ef4abdafc6) that seems to use the term in a sense as what we normally do with macros in Lisp or with templates in C++. The other one is a bit lengthy and I really didn't have patience nor time to…

So I've my self used Lombok but I've been using Kotlin lately. IMHO Kotlin if far far superior in terms of how it provides appropriate constructs that are patches to a stale language (hopefully new release cycle fixes it). So far I've observed with libraries like Lombok there is a smaller community (compared to language community) that vets the idea; and the features are opinionated to that particular community. Which results into fragmentation; just as example https://immutables.github.io/ and https://github.com/google/auto are two libraries providing features like factories and immutable value classes. Then you get articles like https://codeburst.io/lombok-autovalue-and-immutables-or-how-to-write-l… for improving your code. This in my opinion doesn't hurt as long as you are a small company. But when your code is going to be used across teams with different opinions, and language doesn't enforce a single way to define construct these kind of byte-code mangling ideas fall apart. I've personally people complain about Lombok and they hate it every bit. Doing these constructs at language level removes debate, and unifies how people in larger community. I hope newer versions of Java move fast enough to make something simple like `@Cleanup` a thing of past. I will highly encourage everyone to try Kotlin too; it's almost transparent drop-in with better syntax.

while most rdbms-based projects will continue using foreign key constraints (and all will be referentially cast in stone), and postgressives will enjoy 100000x query speedups by remembering to include your hornsnaggle_tree_index_lookup_speeder_upper index, there is a certain fanatical mindset from the rdbms world that sounds a bit like: never forget always include jquery with every web app you make. it's made by real profeshunalz who know more than you and lots of people already included it and you should simply just learn to accept that all front-end web problems have already all been solved by jqueremy and you should simply refactor it all in terms of jqueremy. anything else is korrupshun. In other words, always only ever consider the same tools and techniques. LOL A mere search for other database types produces pages upon pages of "why sql is beating nosql" and all stack overflow answers always doom you to the 7th level of hell for anything but 3rd normalized form. hey let's all use lookup tables for many to many. it's a cult. it's nuts. anyone who has spent any amount of time with database-backed applications is surely aware of the tradeoffs they are making when choosing non-relational databases of any kind. The obsession with forcing every all all use cases into the rdbms mindset makes me say "well then, let's just flatten everything even further into mapped key-value a la ohm." in which one encodes the key with path info and the value with the value, etc. if the…