We focus on Mobile App Development and iOS development is so much smoother in every framework on a Mac over a Windows computer. iOS development in Swift won't work on Windows but looking at the other cross platform frameworks, the chances that your code will just work on an iPhone when you develop on a Windows computer is much lesser. To a certain extent, you can make the UI look similar using Flutter or Webpack for React Native, but once it comes to the device functionality like Wallet, Camera, File Storage, it becomes a bigger pain than it's worth.
Github Actions allowed us to drop previous CI/CD technologies like Jenkins or AWS CodeBuild. The main advantages for us are: - The Infrastructure-as-Code approach of Github Actions enables us to keep CI/CD configurations next to the code. - Github as a single platform for repositories and CI/CD simplifies our stack and effort to manage it on the daily basis.
TVcloud Team <3 Github Actions
One additional feature of TypeScript we're relying heavily on is the ability to generate types for publishing packages. We use this to generate all component typings automatically, based on shared JSON Schema definitions, enabling auto-complete for properties defined in the context of the component... based on the generated types.
I don't know about Bootstrap v5, but Bootstrap v3 and v4 was a nightmare when it comes to RTL. I switched to Vuetify in its early days when their RTL support is not very mature. But given that they care about RTL and have it in their roadmap and considerations, the change proved fruitful after their RTL support matured enough over time (and github issues).
I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?
Need help deciding technology stack. Thanks.
I don't know anything really about CodeIgniter, but I do know that microservices are a great choice for e-commerce, as they tend to have a lot of different moving (but not necessarily connected) parts. That being said, and if you have a choice, I'd recommend Go personally. But node isn't the worst option if Go isn't something you're comfortable with.
If you know typescript and want an entire framework to work with, go wth Angular. AngularJS, to my knowledge was deprecated. React is great, popular, and you'll find a ton of support.
I'm going to sound like a sales rep for Retool in this Stack Decision, but who cares!
Retool has been simply amazing at allowing us to rapidly create backend administrative interfaces for our platforms and services.
We've gone from having a 50:50 split of time spent developing platforms and developing internal tools to a 95:5 split at least!
I've yet to find an API/database/service that Retool hasn't been able to natively interface with, and their support for arbitrary REST/GraphQL APIs means that I don't foresee myself ever finding a truly incompatible source of data.
And to top it all off, Retool's pricing plans are extremely generous considering how much time has been freed up for us.
It's genuinely frightening how easily, agilely, and affordably we've been able to integrate Retool into our various stacks.
I have decided to learn Machine Learning using Python. But, I don't know which is the best IDE to use (specifically for ML) to get high performance. I have been using #Vscode since the beginning when I started learning Python. But now, I feel it's not suitable for Data Analysis, Representing the Data, Visuilaizing and this kind of stuff. Any Advice?
I use spyder because of its interactive side, while also allowing for developing a proper program. I usually run snippets of code, see the outputs either in the ipython console or through the powerful "Variable explorer" window. As the code grows, I build them into functions etc. on the program side. I often use F-9 to run a snippet in the program panel, get insight into the objects, drill down as I like. Many people use jupyter notebooks, but for me Spyder is indispensable when I need to build step by step while exploring, experimenting, etc.
Hi. I am a backend developer in a company tasked with recoding a legacy application, choosing the right technology stack, and then later hiring for that stack.
This is a freight/logistics application made 15 years ago in PHP with no modern framework used. In this application, customers from different countries login into theirs accounts and add a huge number of shipments, like let's say 500, and then, later on, generate PDFs for them after calling third-party APIs. This application has API integrations with lots of other companies and also offers API access to its own software as well. This application is also used in-house by warehouse people to scan different shipments using barcode scanners and to process shipments by performing different actions on them. The database being used currently is MySQL.
Now we have the choice to write this application in a modern technology stack. Performance, speed, reliability, and security are the primary concerns here.
Should I go with Java/Spring Boot with AngularJS as the front end or PHP/Laravel with Vue.js as the front end?
Switching at this point from PHP to Java will not be hard if Java is considered better here because we can hire as per our final decision.
Hi Chris, I will suggest going with Laravel and MySQL since the existing system is already in PHP it will help a lot and easier to port out to Laravel and will save a lot of time. Laravel has a very robust mechanism to handle the jobs/Queues and it comes with a lot of features.
Thank you. Keeping aside the fact that the existing system is made in PHP, would you still recommend Laravel over java? Wont java give better performance and speed over Laravel?
Hi Chris, I recommend you to use Java with spring boot to rewrite your software. You will have the advantages of modern applications. The main challenge will be to cut your existing business logic to functional services (microservices) that will communicate each others. That will comes up also with the challenges of orchestrate those services but for that no worries. For the database also, will recommend Postgre too. For the front end, you can use angular, react or vue js with your backend since it will be API calls.
Hope it can help!
As the Shelf Dev Team grows in size, more and more newly joined engineers face questions specific to our codebase and development setup.
Imagine you try to launch a project locally for development, and then some obscure error comes up with a stack trace pointing to some internal tooling. Obviously, you won't find any help on Google, as it comes from code developed internally.
Usually, more experienced developers help newcomers in Slack. This is the fastest way to get help, but it doesn't scale, it's not repeatable, and usually is lost, since communication happens in direct messages.
That's where Stackoverflow for Teams comes in.
Albeit restricted to only a few places worlwide compared to its peers in the cloud segment, I am yet to find another provider capable of delivering a score over 5000 (Geekbench) in a benchmark on a single CPU machine, and each machine costs $6 a month. For homelab and experienced users who don't need DBaaS or IaaC's, it's a pretty straightforward choice. A more comprehensive review of Vultr's HF machines can be found here.
We chose TickTick after using a bunch of other project management tools that didn't really fit us. As a team, TickTick has made projects enjoyable. We break down projects into very small pieces and take them on one by one and we never miss any detail because of the tool. We have time tracking for each tasks to keep us on time, we share tasks between the team, take notes, and even establish habits throughout the teams so we can get better and better at what we do. We also tend to invite clients in as guests so they can follow along through the process of their project.
Because Seq is lightweight and easy to setup which helped me to setup a centralized logging system without investing too much resources (money and compute power). I know that ELK has more superior features but I didn't need most of them, I just needed a place to store and view logs of backend services.
At Tabulo, we make extensive use of Redis as a state store. However, for common operations, we found ourselves making multiple requests to the Redis server from our Elixir microservice. These network requests became a bottleneck, and so we turned to using Lua scripts that could be run on the context of the Redis server, which would only require one network request per script.
However, the Redis implementation of Lua had its restrictions; for one, we couldn't use require() calls in Lua. There were also times when we wanted to call one Lua script from another, which Redis didn't support (there was an undocumented workaround, but it made debugging a pain). So, we wrote a preprocessor that would replace require() calls with the actual content of the file it was requiring and create generated Lua files that could be read and loaded into the Redis server.
For us, while Lua may not be the most powerful language, it has served us beautifully for writing Redis scripts, especially in combination with Teal.
Which is better of Laravel, Rails and Django for creating great products quickly?
Which is better for creating open source apps that others might want to contribute to?
I want a mature tool for creating web apps that qualifies for:
- Quick prototyping
- Easy to get to production level for backend
- Maintainable and buildable by one person alone
- Enforces conformity, so others can easily read and contribute to the code, making successfully open sourcing possible
- Works well with React
- Has a mature and fairly stable ecosystem for the basics (auth, storage, db, image handling, backups, change history, etc.
- Has an ecosystem that will still be alive in 10 years, responding to changes.
I would have to learn Ruby, Python or PHP for each, so that factors in too.
I'm proficient in React and Node.js, but I feel the node backend ecosystem is too immature with a million different ways to do everything, and too many decisions to make, too much wiring to get everything to work together, and too many packages that end up not being supported a few months down the line.
Which would you choose for me to learn?
Comparing them end-to-end, Rails comes the most productive in my opinion. But there are bolder parameters you may consider. i.e. no one switches from Django to Rails to improve productivity and vice versa (probably from Laravel to one of those two).
The language's productivity also matters, which both Ruby and Python are better for that.
There is a philosophical difference between #Django and #Rails :
Django supports the "Explicit over Implicit" idea, making it easier for newcomers to understand what's going on. This idea also has downsides. This allows beginners to start working with Django without even learning Django and best practices and defer learning by using references like Stackoverflow.com, which is not a good idea because you potentially don't know things that you don't know! Also, you may find many different project styles.
On the other hand, Rails support the "Convention over configuration" and Scaffolding idea. It's easier for a Rails developer to be added to a new project or just review a random Rails project. Everything has a default and also it has some downsides as well. e.g. As a beginner, everything feels like magic in Rails, and you don't understand what is going on and how Rails understand while you didn't "explicitly" say what do you want sometimes.
Conclusion: Rails and Django are more productive and you can build projects on your own quickly (many giant startups launched this way!).Node.JS isn't immature, also sometimes shows better performance comparing the mentioned alternatives. But if you suffer from "a million different ways to do everything" and "many decisions to make", Take Ruby on Rails for sure.
P.S: for learning RoR I suggest the book/video from Michael Hartl.
I picked Django because we use it at work. But honestly, if you don't know any of them, I would look at the jobs around where you live and learn the one that either has the most jobs posted or if you can look at the trends the one that is growing the number of jobs the most.
All three would satisfy your needs and all three are good choices. Dotnet core would also be a good choice, again if there are jobs in your area for said technologies. If you literally don't care about this for employment, learn them all and just do it in alphabetical order :)
Note: I think you are wrong about Node being too immature - there are also MOSTLY standards for everything you want to do on the backend that have not changed for many years.
> you are wrong about Node being too immature
and in course of few years you will end up with tons of broken/outdated dependencies, but with the critical vulnerabilities
I was advised by an instructor that Streamlit was now his favorite tool for deploying Python-based projects. He emphasized the slow learning path for Flask was a hindrance even if it provided more flexibility. He proceeded to give the class an hour long live demonstration of streamlit. I was impressed with how much you can do with just a few basic guidelines. He also mentioned that unlike R's Shiny, Streamlit still didn't chare to host your project beyond a short term demo period.
Are you familiar with Anvil (https://anvil.works/)? As far as I can tell, it's much more powerful than Streamlit and I can't understand why it's not better known.
We recently changed our stack adopting Next.js as our React framework and using Storybook to help build our React components in isolation, our new frontend is written in TypeScript and Ant Design ( UI design language and React UI library ), all logic process in written in Ruby using Sidekiq as background worker and Rspec as testing framework. For delivering data, we use GraphQL and Apoll, Jest and Cypress are used for testing too.
Using vue-property-decorators keeps all the information about a component inside one typescript class. The alternative was to use the old V2 syntax and
Vue.extend() to add props. Using the property decorators helped to keep the code readable, maintainable (since type safety is improved) and made it easier for new developers to get started.
I had a goal to create the simplest accounting software for Mac and Windows to help small businesses in Canada.
This led me to a long 2 years of exploration of the best language that could provide these features:
- Great overall productivity
- International wide-spread usage for long-term sustainability and easy to find documentation
- Versatility for creating websites and desktop softwares
- Enjoyable developper experience
- Ability to create good looking modern UIs
- Job openings with this language
I tried Python, Java, C# and C++ without finding what I was looking for.
I think you should go with Flutter any day because there is a large variety of widgets inventory for it which can fasten up the development time to at least roll out a minimal viable product out there. Performance of Flutter Apps are also better than React Native apps. And as an added bonus, if in future you want to add a web interface for the same, you can do it using the existing codebase if written in Flutter (dart).
I completely agree with this. Just wanted to add that Dart (the language used by flutter) and the design paradigm (fully functional) can be hard at first. Once you tinker with it you can almost create any prototype in no time.
IMO if you need to build a simple and quick UI for your app, I'd suggest you go for either React Native or Android with Java or Better Yet, Kotlin (It won't take much time for you to get familiar with it if you know Java. See this https://play.kotlinlang.org/koans/overview). For Backend APIs you can use Python with something like Flask
We chose Postmark as our transactional email service for several reasons:
Laser-focus (at the time) on transactional email - their success/speed/reliability with delivering transactional email is amazing. Note, they have now branched out and offer marketing/broadcast email services too.
Developer-friendly - Awesome docs and resources. Their Rail gem integrates directly with ActionMailer so nearly all of our code worked without changes.
Servers - You can set up "Servers" for different mail streams/workflows to keep things separate and easy to review.
Bootstrapped - Wildbit (who makes Postmark) is bootstrapped just like the Friendliest.app and they offer a service credit to other bootstrapped startups.
Thanks to some assistance from FastRobot, we got a great Terraform + Chef deployment mechanism that replaced our previous reliance on Amazon OpsWorks after they decided to stop maintaining that service. Having the configuration checked into source control is more powerful than having it all in the GUI with AWS OpsWorks, and we can see the changes as regular pull requests just like our application code.
I have been searching lately for frameworks to build mobile apps.
I think in the long term Flutter would be your best bet, I work with both flutter and react native daily and I am constantly finding reasons why flutter is better then RN, some general things I've found with flutter are the following:
- User base is growing massively and a lot of companies are switching over to flutter
- Performance is much better than React, both usage and compile times.
- Managing framework updates with Flutter is a breeze and not so great with React.
I have been exploring the Flutter lately it's good but if I am building something which is really huge then I will definitely use React Native for these reasons
- React Native is used by so many big companies so there are libraries for everything you need.
- As of now React Native community is bigger and more active than Flutter so if you're stuck anywhere it will be easy to get help or just find a solution from stack overflow.
- Since you're already working on JS you wouldn't need to learn anything new and you can focus on building your product.
The question you should be asking yourself Do I want to spend my time learning a new framework and then build the product or should I just building the product with the framework I know.
First the technical scope did not justify using React, however, the primary decider was made after spending 24 hours with each framework. Vue allowed me to get up and running faster, with more confidence. Had the technical requirements been greater, I would have likely gone with React, partly due to the community size.
Which is better, angular or vue?
I have not used angular. Having said that I don't look at frameworks / technology in comparison to each other, but only in analyzing fit with the known requirements. Certainly from an employment standpoint some technologies / frameworks are in greater demand and that might drive ones adoption. Technology without a need is meaningless...
Our old ZNC IRC bouncer was succeeded by TheLounge , because it includes a Web-Interface, is actively maintained, has an out-of-the-box Docker image and overall just feels "cleaner" and more up-to-date.
It is responsive, offers modern chat features (like embeddings) and includes a search along with chat logs.