pkgsrc VS Grunt

pkgsrc Reviews

Grunt Reviews

pkgsrc mentions (8)

• Installing packages without an internet connection?

  It seems according to pkgsrc.org that pkgin might follow the PKG_PATH environment variable. You're supposed to set PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/$(uname -p)/$(uname -r|cut -f '1 2' -d.)/All/", and according to uname(1), -p gives the processor architecture and -r gives the operating system [kernel] release. Source: about 1 year ago

• pkgsrc.se is no more :(

  It seems like pkgsrc.org hasn’t got the news yet. Source: over 1 year ago

• Slackware 15.0

  I still have a Slackware install that runs some really old stuff I have. I remember working at AN ISP in the 90s and slack was are secure distro. All the important stuff (authentication, configs, etc.) were stored and served from our 'slack pool'. Funny part is now I do a very basic Slackware install that setup pkgsrc (https://pkgsrc.org) on it so I can really experience the best and worst of times! - Source: Hacker News / about 2 years ago

• Cross-platform package management: Comprehensive comparison of Pkgsrc and Ravenports article published

  Today the second article on cross-platform package management has been published. It features a short description of what Pkgsrc and Ravenports are and a longer part on how they compare. The test environment and procedure is covered and of course the results are presented. At the end a conclusion is drawn. Source: over 2 years ago

• First article on cross-platform package management published

  The second one will contain the results of our two months evaluation of Pkgsrc on multiple platforms and a comparison with Ravenports. Source: over 2 years ago

Grunt mentions (14)

• 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... - Source: dev.to / 2 months ago

• 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.... - Source: dev.to / 3 months ago

• Understanding package.json II: Scripts

  Keep scripts independent: Keep your scripts independent of each other to avoid dependency issues. If you need to run one script after another, use a task runner like Gulp or Grunt to define tasks and their dependencies. - Source: dev.to / 10 months ago

• JavaScript Module Bundlers and all that Jazz ✨

  Browserify was great at bundling scripts, but what if we need to transform code - Say compile CoffeeScript to JavaScript, for this, a new group of tools for the web was born, which focussed on running code transforms. These are usually called task runners, and the most popular ones are Grunt and Gulp. - Source: dev.to / about 1 year ago

• The Emperor's New Library

  What we see, a decade ago, are that many of the "popular" libraries, frameworks, and methods, not surprisingly, have gone by the wayside, a lot that have remained in current code as difficult-to-removemodernize legacy cruft (Bower, Gulp, Grunt, Backbone, Angular 1, ...), and then we have the small minority that are still here. Some that remain have had their utility lessened/questioned by platform and language... - Source: dev.to / about 1 year ago