- Apr 2023
-
bugs.ruby-lang.org bugs.ruby-lang.org
-
why not allow block forwarding without capturing: foo(&) foo(1, 2, &)
Tags
Annotators
URL
-
- Jan 2022
-
scattered-thoughts.net scattered-thoughts.netCoding1
-
It's typically taken for granted that better performance must require higher complexity. But I've often had the experience that making some component of a system faster allows the system as a whole to be simpler
-
-
scattered-thoughts.net scattered-thoughts.net
-
The latest SQLite 3.8.7 alpha version is 50% faster than the 3.7.17 release from 16 months ago. [...] This is 50% faster at the low-level grunt work of moving bits on and off disk and search b-trees. We have achieved this by incorporating hundreds of micro-optimizations. Each micro-optimization might improve the performance by as little as 0.05%. If we get one that improves performance by 0.25%, that is considered a huge win. Each of these optimizations is unmeasurable on a real-world system (we have to use cachegrind to get repeatable run-times) but if you do enough of them, they add up.
-
- Mar 2021
-
trailblazer.to trailblazer.to
-
Optimization in this case is nothing crazy, just something I neglected while designing the framework.
-
-
github.com github.com
-
If a UTF8-encoded Ruby string contains unicode characters, then indexing into that string becomes O(N). This can lead to very bad performance in string_end_with_semicolon?, as it would have to scan through the whole buffer for every single file. This commit fixes it to use UTF32 if there are any non-ascii characters in the files.
-
-
github.com github.com
-
What is the point of avoiding the semicolon in concat_javascript_sources
For how detailed and insightful his analysis was -- which didn't elaborate or even touch on his not understanding the reason for adding the semicolon -- it sure appeared like he knew what it was for. Otherwise, the whole issue would/should have been about how he didn't understand that, not on how to keep adding the semicolon but do so in a faster way!
Then again, this comment from 3 months afterwards, indicates he may not think they are even necessary: https://github.com/rails/sprockets/issues/388#issuecomment-252417741
Anyway, just in case he really didn't know, the comment shortly below partly answers the question:
Since the common problem with concatenating JavaScript files is the lack of semicolons, automatically adding one (that, like Sam said, will then be removed by the minifier if it's unnecessary) seems on the surface to be a perfectly fine speed optimization.
This also alludes to the problem: https://github.com/rails/sprockets/issues/388#issuecomment-257312994
But the explicit answer/explanation to this question still remains unspoken: because if you don't add them between concatenated files -- as I discovered just to day -- you will run into this error:
(intermediate value)(...) is not a function at something.source.js:1
, apparently because when it concatenated those 2 files together, it tried to evaluate it as:
({ // other.js })() (function() { // something.js })();
It makes sense that a ; is needed.
-
And no need to walk backwards through all these strings which is surprisingly inefficient in Ruby.
-
Since the common problem with concatenating JavaScript files is the lack of semicolons, automatically adding one (that, like Sam said, will then be removed by the minifier if it's unnecessary) seems on the surface to be a perfectly fine speed optimization.
-
reducing it down to one call significantly speeds up the operation.
-
I feel like the walk in string_end_with_semicolon? is unnecessarily expensive when having an extra semicolon doesn't invalidate any JavaScript syntax.
-
- Dec 2020
-
github.com github.com
-
The template language's restrictions compared to JavaScript/JSX-built views are part of Svelte's performance story. It's able to optimize things ahead of time that are impossible with dynamic code because of the constraints. Here's a couple tweets from the author about that
-
- Nov 2020
-
github.com github.com
-
It's fast. The Dart VM is highly optimized, and getting faster all the time (for the latest performance numbers, see perf.md). It's much faster than Ruby, and close to par with C++.
-
- Oct 2020
-
medium.com medium.com
-
In the vast majority of cases there’s nothing wrong about wasted renders. They take so little resources that it is simply undetectable for a human eye. In fact, comparing each component’s props to its previous props shallowly (I’m not even talking about deeply) can be more resource extensive then simply re-rendering the entire subtree.
-
- Jul 2020
-
svelte.dev svelte.dev
-
In some frameworks you may see recommendations to avoid inline event handlers for performance reasons, particularly inside loops. That advice doesn't apply to Svelte — the compiler will always do the right thing, whichever form you choose.
-
- Aug 2019
-
hypothes.is hypothes.is
-
Centric web solution is the renowned best web development company.
We have a very highly experienced and expert development team who are experts in web design & development.
We provide various services like Wordpress web development, eCommerce web development, Wordpress theme design and plugin development, website maintenance & optimization.
For more our services call us on +91 98587 58541 or visit our website https://www.centricwebsolution.com/.
Our Services Are:-
- Web Design & Development
- WordPress Development
- WooCommerce Development
- Custom Web Application Development
- Website Migration Services
- Website Maintenance & Performance optimization
- Website Plugin and API Development
- Website Store Optimization
- PHP Web Development
- Enterprise Web Application Development
- Laravel Development Services
- Angularjs Development Services
Tags
- WooCommerce Development
- PHP Web Development
- Laravel Development Services
- Website Plugin and API Development
- Angularjs Development Services
- Website Maintenance & Performance optimization
- Enterprise Web Application Development
- Website Store Optimization
- Web Design & Development
- Website Migration Services
- Custom Web Application Development
Annotators
URL
-