What is MJML and what are its top alternatives?
MJML is a responsive email framework that allows users to easily create responsive emails that render correctly across various email clients. It provides a set of semantic syntax elements that automatically expand into HTML markup. Some key features of MJML include mobile responsiveness, easy integration with popular email providers, and an intuitive syntax. However, limitations of MJML include a learning curve for beginners and limited customizability compared to hand-coding HTML emails.
- Foundation for Emails: Foundation for Emails is a front-end framework for creating responsive HTML emails. It offers a grid system, typography, and components for building emails. Pros of Foundation for Emails include robust customization options and extensive documentation, while a con is the steep learning curve for beginners.
- Antwort: Antwort is an open-source responsive email layout that offers a simple grid system and styles for creating email templates. Pros of Antwort include its flexibility and easy-to-use layout, while a con is limited community support compared to more popular frameworks like MJML.
- Ink: Ink is a responsive email framework by ZURB that provides a grid system and styles for creating email templates. Pros of Ink include its simplicity and compatibility with various email clients, while a con is the lack of frequent updates compared to other frameworks.
- Cerberus: Cerberus is a collection of responsive email patterns that can be easily customized to create email templates. Pros of Cerberus include its modular design and compatibility with major email clients, while a con is the limited number of pre-designed components available.
- Maizzle: Maizzle is a framework that allows for building HTML emails in a more modern way using Tailwind CSS. Pros of Maizzle include its flexibility and ease of use for developers familiar with Tailwind CSS, while a con is the reliance on external libraries for customization.
- Postcards: Postcards is an online tool for creating responsive email templates with a drag-and-drop editor. Pros of Postcards include its user-friendly interface and ready-to-use templates, while a con is the limited ability to customize templates compared to code-based frameworks.
- BEE Free: BEE Free is an online tool that offers a simple drag-and-drop editor for creating responsive email designs. Pros of BEE Free include its ease of use for beginners and a wide range of design elements, while a con is the reliance on the BEE Pro subscription for more advanced features.
- Taxi for Email: Taxi for Email is a platform that streamlines the email template creation process with collaboration features and reusable components. Pros of Taxi for Email include its collaborative capabilities and efficient workflow, while a con is the premium pricing model for full access to all features.
- Chamaileon: Chamaileon is an online email editor that allows for collaborative email design, version control, and template management. Pros of Chamaileon include its team-friendly features and customizable templates, while a con is the limited integration options compared to other platforms.
- Stripo: Stripo is an email design platform with a drag-and-drop editor and collaborative features for creating responsive email templates. Pros of Stripo include its user-friendly interface and extensive library of pre-designed blocks, while a con is the pricing structure for access to premium features.
Top Alternatives to MJML
- Foundation
Foundation is the most advanced responsive front-end framework in the world. You can quickly prototype and build sites or apps that work on any kind of device with Foundation, which includes layout constructs (like a fully responsive grid), elements and best practices. ...
- Bootstrap
Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...
- JavaScript
JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...
- Python
Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best. ...
- Node.js
Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...
- HTML5
HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997. ...
- PHP
Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. ...
- Java
Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere! ...
MJML alternatives & related posts
- Responsive grid160
- Mobile first93
- Open source80
- Semantic75
- Customizable72
- Quick to prototype52
- Simple ui50
- Fast45
- Best practices44
- Easy setup39
- Neutral style6
- HTML, SCSS and JS6
- Accessibility support5
- Professional5
- Xy grid3
- Sass2
- Every new version is smaller, smarter & more efficient2
- Robust1
- Requires jQuery5
- Awful site4
related Foundation posts
ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.
ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import
statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.
React Helmet was chosen to handle <head>
content, because it works universally, making it easy to throw back the correct <title>
and other tags on the initial render, as well as inject new tags for subsequent client-side views.
styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style>
tags when using #StyledComponents.
React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.
Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.
Should I go with Foundation CSS instead of Bootstrap? Or, if any other popular responsive frameworks are out there, please suggest them to me. My site mainly targets mobile or tablet
Bootstrap
- Responsiveness1.6K
- UI components1.2K
- Consistent943
- Great docs779
- Flexible677
- HTML, CSS, and JS framework472
- Open source411
- Widely used375
- Customizable368
- HTML framework242
- Popular77
- Easy setup77
- Mobile first77
- Great grid system58
- Great community52
- Future compatibility38
- Integration34
- Very powerful foundational front-end framework28
- Standard24
- Javascript plugins23
- Build faster prototypes19
- Preprocessors18
- Grids14
- Good for a person who hates CSS9
- Clean8
- Love it4
- Easy to setup and learn4
- Rapid development4
- Great and easy to use3
- Devin schumacher rules2
- Boostrap2
- Community2
- Provide angular wrapper2
- Great and easy2
- Powerful grid system, Rapid development, Customization2
- Great customer support2
- Popularity2
- Clean and quick frontend development2
- Great and easy to make a responsive website2
- Sprzedam opla2
- Easy to use2
- Intuitive1
- Material-ui1
- The fame1
- Numerous components1
- Responsive design1
- Felxible, comfortable, user-friendly1
- Easy setup21
- Design Agnostic1
- Painless front end development1
- So clean and simple1
- Recognizable1
- It's fast1
- Geo1
- Pre-Defined components1
- Not tied to jQuery1
- Love the classes?1
- Poop1
- Vue1
- Javascript is tied to jquery26
- Every site uses the defaults16
- Grid system break points aren't ideal15
- Too much heavy decoration in default look14
- Verbose styles8
- Super heavy1
related Bootstrap posts
I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.
I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).
As per my work experience and knowledge, I have chosen the followings stacks to this mission.
UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.
Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.
Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.
Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.
Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.
Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.
Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.
Happy Coding! Suggestions are welcome! :)
Thanks, Ganesa
For Etom, a side project. We wanted to test an idea for a future and bigger project.
What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.
You kind of need a map to work as a proxy between the software and Google Maps API.
We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.
Thanks to all the people behind Create React App it's easier to start any React application.
We also chose a module called Reactstrap which is Bootstrap UI in React components.
An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to
Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.
JavaScript
- Can be used on frontend/backend1.7K
- It's everywhere1.5K
- Lots of great frameworks1.2K
- Fast899
- Light weight746
- Flexible425
- You can't get a device today that doesn't run js392
- Non-blocking i/o286
- Ubiquitousness237
- Expressive191
- Extended functionality to web pages55
- Relatively easy language49
- Executed on the client side46
- Relatively fast to the end user30
- Pure Javascript25
- Functional programming21
- Async15
- Full-stack13
- Its everywhere12
- Future Language of The Web12
- Setup is easy12
- JavaScript is the New PHP11
- Because I love functions11
- Like it or not, JS is part of the web standard10
- Everyone use it9
- Can be used in backend, frontend and DB9
- Easy9
- Expansive community9
- For the good parts8
- Easy to hire developers8
- No need to use PHP8
- Most Popular Language in the World8
- Powerful8
- Can be used both as frontend and backend as well8
- It's fun7
- Its fun and fast7
- Popularized Class-Less Architecture & Lambdas7
- Agile, packages simple to use7
- Supports lambdas and closures7
- Love-hate relationship7
- Photoshop has 3 JS runtimes built in7
- Evolution of C7
- Hard not to use7
- Versitile7
- Nice7
- Easy to make something6
- Can be used on frontend/backend/Mobile/create PRO Ui6
- 1.6K Can be used on frontend/backend6
- Client side JS uses the visitors CPU to save Server Res6
- It let's me use Babel & Typescript6
- Clojurescript5
- Everywhere5
- Scope manipulation5
- Function expressions are useful for callbacks5
- Stockholm Syndrome5
- Promise relationship5
- Client processing5
- What to add5
- Because it is so simple and lightweight4
- Only Programming language on browser4
- Subskill #41
- Test21
- Easy to understand1
- Not the best1
- Easy to learn1
- Hard to learn1
- Easy to learn and test1
- Love it1
- Test1
- Hard 彤0
- A constant moving target, too much churn22
- Horribly inconsistent20
- Javascript is the New PHP15
- No ability to monitor memory utilitization9
- Shows Zero output in case of ANY error8
- Thinks strange results are better than errors7
- Can be ugly6
- No GitHub3
- Slow2
- HORRIBLE DOCUMENTS, faulty code, repo has bugs0
related JavaScript posts
Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.
But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.
But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.
Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.
How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:
Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.
Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:
https://eng.uber.com/distributed-tracing/
(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)
Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark
Python
- Great libraries1.2K
- Readable code965
- Beautiful code848
- Rapid development789
- Large community692
- Open source439
- Elegant394
- Great community283
- Object oriented274
- Dynamic typing222
- Great standard library78
- Very fast62
- Functional programming56
- Easy to learn52
- Scientific computing47
- Great documentation36
- Productivity30
- Matlab alternative29
- Easy to read29
- Simple is better than complex25
- It's the way I think21
- Imperative20
- Very programmer and non-programmer friendly19
- Free19
- Powerfull language17
- Machine learning support17
- Fast and simple16
- Scripting14
- Explicit is better than implicit12
- Ease of development11
- Clear and easy and powerfull10
- Unlimited power9
- It's lean and fun to code8
- Import antigravity8
- Print "life is short, use python"7
- Python has great libraries for data processing7
- Although practicality beats purity6
- Fast coding and good for competitions6
- There should be one-- and preferably only one --obvious6
- High Documented language6
- Readability counts6
- Rapid Prototyping6
- I love snakes6
- Now is better than never6
- Flat is better than nested6
- Great for tooling6
- Great for analytics5
- Web scraping5
- Lists, tuples, dictionaries5
- Complex is better than complicated4
- Socially engaged community4
- Plotting4
- Beautiful is better than ugly4
- Easy to learn and use4
- Easy to setup and run smooth4
- Simple and easy to learn4
- Multiple Inheritence4
- CG industry needs4
- List comprehensions3
- Powerful language for AI3
- Flexible and easy3
- It is Very easy , simple and will you be love programmi3
- Many types of collections3
- If the implementation is easy to explain, it may be a g3
- If the implementation is hard to explain, it's a bad id3
- Special cases aren't special enough to break the rules3
- Pip install everything3
- No cruft3
- Generators3
- Import this3
- Can understand easily who are new to programming2
- Securit2
- Should START with this but not STICK with This2
- A-to-Z2
- Because of Netflix2
- Only one way to do it2
- Better outcome2
- Good for hacking2
- Batteries included2
- Procedural programming2
- Sexy af1
- Automation friendly1
- Slow1
- Best friend for NLP1
- Powerful0
- Keep it simple0
- Ni0
- Still divided between python 2 and python 353
- Performance impact28
- Poor syntax for anonymous functions26
- GIL22
- Package management is a mess19
- Too imperative-oriented14
- Hard to understand12
- Dynamic typing12
- Very slow12
- Indentations matter a lot8
- Not everything is expression8
- Incredibly slow7
- Explicit self parameter in methods7
- Requires C functions for dynamic modules6
- Poor DSL capabilities6
- No anonymous functions6
- Fake object-oriented programming5
- Threading5
- The "lisp style" whitespaces5
- Official documentation is unclear.5
- Hard to obfuscate5
- Circular import5
- Lack of Syntax Sugar leads to "the pyramid of doom"4
- The benevolent-dictator-for-life quit4
- Not suitable for autocomplete4
- Meta classes2
- Training wheels (forced indentation)1
related Python posts
How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:
Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.
Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:
https://eng.uber.com/distributed-tracing/
(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)
Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark
Hi, I have an LMS application, currently developed in Python-Django.
It works all very well, students can view their classes and submit exams, but I have noticed that some students are sharing exam answers with other students and let's say they already have a model of the exams.
I want with the help of artificial intelligence, the exams to have different questions and in a different order for each student, what technology should I learn to develop something like this? I am a Python-Django developer but my focus is on web development, I have never touched anything from A.I.
What do you think about TensorFlow?
Please, I would appreciate all your ideas and opinions, thank you very much in advance.
Node.js
- Npm1.4K
- Javascript1.3K
- Great libraries1.1K
- High-performance1K
- Open source805
- Great for apis487
- Asynchronous477
- Great community425
- Great for realtime apps390
- Great for command line utilities296
- Websockets86
- Node Modules84
- Uber Simple69
- Great modularity59
- Allows us to reuse code in the frontend58
- Easy to start42
- Great for Data Streaming35
- Realtime32
- Awesome28
- Non blocking IO25
- Can be used as a proxy18
- High performance, open source, scalable17
- Non-blocking and modular16
- Easy and Fun15
- Easy and powerful14
- Future of BackEnd13
- Same lang as AngularJS13
- Fullstack12
- Fast11
- Scalability10
- Cross platform10
- Simple9
- Mean Stack8
- Great for webapps7
- Easy concurrency7
- Typescript6
- Fast, simple code and async6
- React6
- Friendly6
- Control everything5
- Its amazingly fast and scalable5
- Easy to use and fast and goes well with JSONdb's5
- Scalable5
- Great speed5
- Fast development5
- It's fast4
- Easy to use4
- Isomorphic coolness4
- Great community3
- Not Python3
- Sooper easy for the Backend connectivity3
- TypeScript Support3
- Blazing fast3
- Performant and fast prototyping3
- Easy to learn3
- Easy3
- Scales, fast, simple, great community, npm, express3
- One language, end-to-end3
- Less boilerplate code3
- Npm i ape-updating2
- Event Driven2
- Lovely2
- Creat for apis1
- Node0
- Bound to a single CPU46
- New framework every day45
- Lots of terrible examples on the internet40
- Asynchronous programming is the worst33
- Callback24
- Javascript19
- Dependency hell11
- Dependency based on GitHub11
- Low computational power10
- Very very Slow7
- Can block whole server easily7
- Callback functions may not fire on expected sequence7
- Breaking updates4
- Unstable4
- Unneeded over complication3
- No standard approach3
- Bad transitive dependency management1
- Can't read server session1
related Node.js posts
Needs advice on code coverage tool in Node.js/ExpressJS with External API Testing Framework
Hello community,
I have a web application with the backend developed using Node.js and Express.js. The backend server is in one directory, and I have a separate API testing framework, made using SuperTest, Mocha, and Chai, in another directory. The testing framework pings the API, retrieves responses, and performs validations.
I'm currently looking for a code coverage tool that can accurately measure the code coverage of my backend code when triggered by the API testing framework. I've tried using Istanbul and NYC with instrumented code, but the results are not as expected.
Could you please recommend a reliable code coverage tool or suggest an approach to effectively measure the code coverage of my Node.js/Express.js backend code in this setup?
I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery
For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:
Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have
GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.
MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website
- New doctype448
- Local storage389
- Canvas334
- Semantic header and footer285
- Video element240
- Geolocation121
- Form autofocus106
- Email inputs100
- Editable content85
- Application caches79
- Easy to use10
- Cleaner Code9
- Easy5
- Websockets4
- Semantical4
- Audio element3
- Content focused3
- Better3
- Modern3
- Compatible2
- Very easy to learning to HTML2
- Semantic Header and Footer, Geolocation, New Doctype2
- Portability2
- Easy to forget the tags when you're a begginner2
- Long and winding code1
related HTML5 posts
Hey guys, I need some advice on one thing. Currently, I am a fresher and know HTML5, CSS, JavaScript, PHP and, MySQL. Recently I got a client project through one of my friends and he wants me to build an E-learning Management System. Are these skills enough to build an LMS website?
Thanks in advance!! ;)
Few years ago we were building a Next.js site with a few simple forms. This required handling forms validation and submission, but instead of picking some forms library, we went with plain JavaScript and constraint validation API in HTML5. This shaved off a few KBs of dependencies and gave us full control over the validation behavior and look. I describe this approach, with its pros and cons, in a blog post.
PHP
- Large community954
- Open source820
- Easy deployment767
- Great frameworks487
- The best glue on the web387
- Continual improvements235
- Good old web185
- Web foundation145
- Community packages135
- Tool support125
- Used by wordpress35
- Excellent documentation34
- Used by Facebook29
- Because of Symfony23
- Dynamic Language21
- Easy to learn17
- Cheap hosting17
- Very powerful web language15
- Awesome Language and easy to implement14
- Fast development14
- Because of Laravel14
- Composer13
- Flexibility, syntax, extensibility12
- Easiest deployment9
- Readable Code8
- Fast8
- Most of the web uses it7
- Short development lead times7
- Worst popularity quality ratio7
- Fastestest Time to Version 1.0 Deployments7
- Faster then ever6
- Simple, flexible yet Scalable6
- Open source and large community5
- Easy to use and learn4
- Great developer experience4
- Has the best ecommerce(Magento,Prestashop,Opencart,etc)4
- Is like one zip of air4
- Open source and great framework4
- Large community, easy setup, easy deployment, framework4
- Cheap to own4
- Easy to learn, a big community, lot of frameworks4
- I have no choice :(4
- Hard not to use2
- Great flexibility. From fast prototyping to large apps2
- Interpreted at the run time2
- Walk away2
- FFI2
- Safe the planet2
- Used by STOMT2
- Fault tolerance2
- Simplesaml1
- Secure1
- It can get you a lamborghini1
- Bando1
- Secure0
- Largr community0
- So easy to learn, good practices are hard to find21
- Inconsistent API16
- Fragmented community8
- Not secure6
- No routing system3
- Hard to debug3
- Old2
related PHP posts
When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?
So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.
React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.
Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.
Hello, I am building a website for a school that's used by students to find Zoom meeting links, view their marks, and check course materials. It is also used by the teachers to put the meeting links, students' marks, and course materials.
I created a similar website using HTML, CSS, PHP, and MySQL. Now I want to implement this project using some frameworks: Next.js, ExpressJS and use PostgreSQL instead of MYSQL
I want to have some advice on whether these are enough to implement my project.
Java
- Great libraries607
- Widely used446
- Excellent tooling401
- Huge amount of documentation available396
- Large pool of developers available334
- Open source209
- Excellent performance203
- Great development158
- Used for android150
- Vast array of 3rd party libraries148
- Compiled Language61
- Used for Web53
- High Performance47
- Managed memory46
- Native threads45
- Statically typed43
- Easy to read35
- Great Community33
- Reliable platform29
- JVM compatibility24
- Sturdy garbage collection24
- Cross Platform Enterprise Integration22
- Good amount of APIs20
- Universal platform20
- Great Support18
- Great ecosystem14
- Lots of boilerplate11
- Backward compatible11
- Everywhere10
- Excellent SDK - JDK9
- It's Java8
- Static typing7
- Cross-platform7
- Mature language thus stable systems6
- Better than Ruby6
- Long term language6
- Portability6
- Vast Collections Library5
- Clojure5
- Used for Android development5
- Most developers favorite4
- Old tech4
- Best martial for design4
- Javadoc3
- History3
- Testable3
- Great Structure3
- Stable platform, which many new languages depend on3
- Type Safe2
- Faster than python2
- Makes code organized1
- Job0
- Verbosity33
- NullpointerException27
- Nightmare to Write17
- Overcomplexity is praised in community culture16
- Boiler plate code12
- Classpath hell prior to Java 98
- No REPL6
- No property4
- Code are too long3
- Non-intuitive generic implementation2
- There is not optional parameter2
- Floating-point errors2
- Java's too statically, stronglly, and strictly typed1
- Returning Wildcard Types1
- Terrbible compared to Python/Batch Perormence1
related Java posts
How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:
Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.
Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:
https://eng.uber.com/distributed-tracing/
(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)
Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark
When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.