Light Table
webpack
Light Table | webpack | |
---|---|---|
10 | 331 | |
11,740 | 64,179 | |
- | 0.2% | |
0.0 | 9.8 | |
almost 2 years ago | 1 day ago | |
Clojure | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Light Table
-
Light Table
https://github.com/LightTable/LightTable
Looks like the project has been archived
- Ask HN: More “experimental“ UIs for editing/writing code?
-
A Source Code Path Visualizer
I think LightTable development stalled out when the original creator left the project in 2015. Likely the project was too ambitious and maybe ahead of its time. Or maybe Clojure was not the right language to build an IDE...
-
Ask HN: Best Dev Tool pitches of all time?
I think the closest we got to a closure of Light Table is this: https://chris-granger.com/2014/10/01/beyond-light-table/
Which includes:
> Light Table will continue to go on strong. We haven’t talked too much about it lately, but it’s used by tens of thousands of people and still growing. We use it every day to help us build Eve and thanks to the awesome people in the community that has sprung up around it, it gets better every week.
Judging by GitHub contribution data (https://github.com/LightTable/LightTable/graphs/contributors...), it seems there has only been 25 commits (from one author) since Sep 20, 2019.
-
AWESOME WINDOWS TOOLS
Light Table - A customizable editor with instant feedback and showing data values flow through your code.
- [번역] From node-webkit to Electron 1.0
-
Are there extensible environments in the manner of Emacs outside of text editors and developer tools generally?
Most IDEs nowadays are as extensible as Emacs is, but most people don't think of them as app platforms, they think of them as IDEs, so they don't bother craeting Email or IRC clients for their IDEs: - Racket's own DrRacket IDE is pretty extensible, although no one seems to try to extend it with apps like Magit, Org-Mode, Calc, or whatever other useful features that Emacs provides. It is theoretically possible, but it just hasn't happened yet. - LightTable is a powerful programming editor written and extensible in Clojure. - Gnome's Gedit can be scripted in Python.
-
Emacs on Graal
I think it would be better to create an Emacs Lisp interpreter in Clojure for the LightTable editor.
-
Code Shelter: collective to help maintain popular OSS whose authors need a hand or don't have the time any more
It looks like it's not completely abandoned, at least. https://github.com/LightTable/LightTable/discussions/2506
-
Cider 1.0
I'm no Bozhidar, but thought I'd share some links you might find interesting:
- https://github.com/LightTable/LightTable - Clojure editor made in Clojure, not sure if it's being maintained anymore, core authors moved on to a different project if I remember correctly.
- https://github.com/mogenslund/liquid - Clojure editor made in Clojure, fairly new and basic but has a pretty tight integration with Clojure (itself really) which makes it interesting and it can also be embedded into other applications (or embed your other applications into Liquid)
- https://github.com/Olical/conjure - My daily driver for Clojure development. Is not an editor by itself, but it's written in Clojure, and exposed to neovim as a vim plugin. Not only supports Clojure, but also Fennel, Janet and Racket so far. Pretty handy if you sometimes like to dive into Clojure-like languages that are not Clojure (or Racket).
webpack
-
Practical and Beginner friendly guide for speeding up your web-apps
There are various tools available that manage the size of bundled assets. We are going to use the example of a popular and widely used bundler named Webpack, and practically look at many of the optimization techniques it offers.
-
Getting started with TiniJS framework
Homepage: https://webpack.js.org/
-
Optimizing React Apps for Performance: A Comprehensive Guide
Click "Start Test." WebPageTest generates a comprehensive report with details about the loading process, including time to first byte (TTFB), page load time, and visual progress. ### Setting Benchmarks with Lighthouse Start with Lighthouse audits to maximize the performance of your React application. Evaluate Lighthouse's scores and suggestions with careful consideration. Next, set benchmarks that are in line with industry norms or customized to meet your unique performance goals. Lastly, pay close attention to the places in your application where it needs work. You can improve your React application's effectiveness by carefully following these procedures, which will guarantee that it satisfies the required performance requirements. ### Analyzing Performance Results with WebPageTest In order to fully evaluate your webpage's performance, launch WebPageTest with a variety of systems, simulating a variety of user scenarios. Examine the waterfall chart carefully to identify loading patterns and bottlenecks, which are essential for improving the user experience. To see the page's rendering process over time and do a thorough examination, use filmstrip views. To effectively assess performance, pay special attention to measures such as time to first byte (TTFB), start render time, and fully loaded time. Also, a better understanding of performance variances is made possible by comparing findings across various test designs, which helps make well-informed recommendations for improving webpage responsiveness and efficiency. ## Impact of third-party libraries on React app performance Third-party library integration can speed up development while improving functionality in our React application. It's crucial to consider the possible effects on performance, though. Because heavy or poorly optimized libraries might negatively impact the speed and usability of our application. ### Bundle Size Look at the distribution file sizes related to the library, and use tools such as Bundlephobia or Webpack Bundle Analyzer to fully evaluate their impact on your bundle size. This thorough analysis enables you to make well-informed decisions about whether to include the library, making sure that its contribution minimizes superfluous bulk in your application's codebase and is in line with your optimization goals. ### Network Requests Analyze how the third-party library affects network requests to maximize performance. Reduce the number of requests made overall by minimizing external dependencies. This will enhance the user experience and loading speeds. Select appropriate libraries, maximize asset delivery, and leverage code splitting to load components asynchronously. You may improve the effectiveness and responsiveness of your application and provide users with a better experience by cutting down on pointless network queries. ### Execution Time Examine the library's code for any possible performance problems or bottlenecks in order to analyze the runtime performance of the library. Look for places where the code may execute slowly or inefficiently. You may ensure smoother operation inside your application by identifying and addressing any areas of the library's implementation that may be impeding ideal performance by doing a comprehensive assessment. ### Code Splitting for Third-Party Libraries Implementing code splitting is an effective strategy to load third-party libraries only when they are required, reducing the initial page load time. Use dynamic imports to load the library lazily:
- Creating Nx Workspace with Eslint, Prettier and Husky Configuration
-
Google: Angular and Wiz Are Merging
Thanks for the thorough answer!
I confess I wasn't thinking about a particular build tool. My recent experience has been with Vite, where I took a similar approach to what you describe, but haven't had to dig deep into bundle performance because that's not a bottleneck for our application. The last time I did deeper work on the subject was years ago with Webpack.
I thought Webpack at least did dead-code elimination before splitting things into chunks. If I'm reading this random GitHub issue[1] right (and the asker is also right), Webpack does partially behave as I expected, but the pre-chunking optimization pass occurs before things like constant expression evaluation.
[1] https://github.com/webpack/webpack/issues/16672
-
JS Toolbox 2024: Bundlers and Test Frameworks
Webpack is a powerful and widely-used module bundler for JavaScript applications. It’s known for its flexibility and extensive plugin system, making it a popular tool in complex web development projects.
-
Webpack: The Web Module Bundler
Thats all about Webpack Basic, there are lots of feature of webpack, You can check here: https://webpack.js.org/
-
How to improve page load speed and response times: A comprehensive guide
Many web pages use CSS and JavaScript files to handle various features and styles. Each file, however, requires a separate HTTP request, which can slow down page loading. Concatenation comes into play here. It involves combining multiple CSS or JavaScript files into a single file. As a result, pages load faster, reducing the time spent requesting individual files. Gulp, Grunt, and Webpack are some of the tools that can assist you in speeding up the concatenation process. They enable seamless merging of many files during development, ensuring deployment readiness.
-
Build a Vite 5 backend integration with Flask
Once you build a simple Vite backend integration, try not to complicate Vite's configuration unless you absolutely must. Vite has become one of the most popular bundlers in the frontend space, but it wasn't the first and it certainly won't be the last. In my 7 years of building for the web, I've used Grunt, Gulp, Webpack, esbuild, and Parcel. Snowpack and Rome came-and-went before I ever had a chance to try them. Bun is vying for the spot of The New Hotness in bundling, Rome has been forked into Biome, and Vercel is building a Rust-based Webpack alternative.
-
Top 20 Frontend Interview Questions With Answers
Webpack is a module bundler, the main purpose of which is to bundle JavaScript files to make them usable in a browser.
What are some alternatives?
Atom - :atom: The hackable text editor
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
Visual Studio Code - Visual Studio Code
esbuild - An extremely fast bundler for the web
GNU Emacs - Mirror of GNU Emacs
vite - Next generation frontend tooling. It's fast!
Brackets - An open source code editor for the web, written in JavaScript, HTML and CSS.
Rollup - Next-generation ES module bundler
intellij-community - IntelliJ IDEA Community Edition & IntelliJ Platform
gulp - A toolkit to automate & enhance your workflow
Vim - The official Vim repository
parcel - The zero configuration build tool for the web. 📦🚀