1678450704
在本教程中,您將學習:什麼是 Visual Studio?什麼是 Visual Studio 代碼?“Visual Studio”和“Visual Studio Code”有什麼區別?“Visual Studio”和“Visual Studio Code”應該選哪個?Visual Studio 與 Visual Studio Code——這些 IDE 代碼編輯器有何區別?
第一次聽說“Visual Studio”,我以為它和“Visual Studio Code”一樣。我不知道為什麼微軟決定用這兩個開發工具的名字來混淆大家。但這是另一天的故事。
“Visual Studio”和“Visual Studio Code”不是一回事。Visual Studio 是一個集成開發環境 (IDE),而 Visual Studio Code 是一個與 Sublime Text 和 Atom 類似的富文本編輯器。
但是這些工具之間的區別不僅僅是 IDE 和文本編輯器。
IDE 是用於編寫、編輯、調試和運行代碼的強大工具。文本編輯器只允許您編寫和編輯代碼。您可能必須退出文本編輯器才能運行您的代碼或下載插件來幫助它為您運行。
在本文中,您將了解 Visual Studio 和 Visual Studio Code 之間的主要區別。但首先,在深入了解這些差異之前,我們需要了解什麼是“Visual Studio”以及什麼是“Visual Studio Code”。
Visual Studio 於 1997 年由 Microsoft 首次發布。它是一個集成開發環境 (IDE),用於開發、編輯和調試網站、Web 和移動應用程序以及雲服務。
因為它是一個 IDE,調試器、編譯器、智能等編程實用程序都已為您捆綁到其中。
Visual Studio 內置了對 C# 和 .NET 的支持。它還支持其他編程語言,如 C、C++、Python、F#、網絡語言(HTML、CSS、JavaScript)等等。Visual Studio 2017 中刪除了對 Java 的支持。
Visual Studio 在 Windows 和 Mac 上運行。它有 3 個版本——社區版、專業版和企業版。社區版是免費的,而專業版和企業版則不是。
Windows 上的安裝比 Mac 更可靠。因此,在 Windows 上,您可能需要下載超過 42 GB 的文件,具體取決於您要執行的操作。
但在 Mac 上,截至撰寫本文時,您需要大約 6.2 GB 的磁盤空間。
Visual Studio Code(也稱為 VS Code)就像 Visual Studio 的迷你版。它是一個開源的輕量級文本編輯器,可在 Windows、Mac 和 Linux 上使用。還有 web 版本可在https://vscode.dev/.
VS Code 內置了對 JavaScript、TypeScript 和 Node JS 的支持,但您可以使用它以您想要的任何語言進行編碼。您需要做的就是下載相關的擴展。
一些擴展由 Microsoft 製作,但很多其他擴展是第三方擴展。
與 Visual Studio 不同,您不需要太多空間即可下載 VS Code。下載它可能不需要超過 200 MB 的磁盤空間。
由於它默認支持 JavaScript、TypeScript 和 Node JS,因此您也可以獲得調試器和智能。但是要獲得其他語言的智能、編譯器和調試器,您必須下載相關的擴展。
現在您知道 Visual Studio 是一個 IDE,而 Visual Studio Code 是一個文本編輯器。那麼接下來讓我們總結一下它們的主要區別。
基礎 | 視覺工作室 | 視覺工作室代碼 |
---|---|---|
類型 | Visual Studio 是一個成熟的 IDE | VS Code 是一個文本編輯器(AKA 代碼編輯器) |
平台 | Visual Studio 在 Windows 和 Mac 上運行 | VS Code 在 Windows、Mac 和 Linux 上運行 |
尺寸 | Visual Studio 比較大。您可能需要在 Windows 上下載超過 40 GB,在 Mac 上下載超過 6 GB | VS Code 在任何平台上都不需要超過 200 MB |
支持 | Visual Studio 內置了對 C# 和 .NET 的支持,以及除 Java 之外的幾種常用語言 | VS Code 開箱即用地支持 JavaScript、Typescript 和 Node JS。它還支持其他編程語言——只要有相應的擴展 |
價錢 | Visual Studio 社區版是免費的,但專業版和企業版的代碼分別為每月 45 美元和 250 美元。 | VS 代碼是免費的。大多數擴展也是免費的,但也有免費增值的 |
擴展 | Visual Studio 沒有 VS Code 那樣多的擴展 | VS Code 有許多專業和精心策劃的擴展,用於各種目的 |
關於在 Visual Studio 和 Visual Studio Code 之間選擇哪個更好以及選擇哪個的爭論由來已久。嗯,這取決於你在做什麼。
如果你只使用 Visual Studio 支持的語言(如 C#、C、C++、Python 等)進行開發,Visual Studio 或其他相關 IDE 可能是你的最佳選擇。
但即使您使用這些語言進行開發,但需要 React、Vue 或 Angular 前端,VS 代碼也可能是您的最佳選擇。
如果您在團隊中工作,他們可能會為您提供企業版 Visual Studio,或與您使用的語言相關的任何其他 IDE。例如,用於 Python 的 PyCharm 和用於 Java 的 IntelliJ Idea。
如果您使用的是 Linux,則必須選擇 Visual Studio Code 或除 Visual Studio 之外的其他一些 IDE。那是因為 Visual Studio 不在 Linux 上運行。
如果您是那種喜歡根據自己的喜好自定義編輯器的人,請選擇 VS Code,因為它具有高度可定制性。如果您正在混合技術,您也應該選擇 VS Code。
本文向您展示了 Visual Studio 和 VS Code 之間的區別,以及它們各自的區別。
爭論永遠不應該是哪個比另一個更好,而應該是哪個最適合你想做的或你需要的。這就是為什麼我們研究了一些可能會鼓勵您選擇一個而不是另一個的場景。
感謝您閱讀。
資料來源: https: //www.freecodecamp.org
#visualstudio #visualstudiocode #vscode
1675304280
We are back with another exciting and much-talked-about Rails tutorial on how to use Hotwire with the Rails application. This Hotwire Rails tutorial is an alternate method for building modern web applications that consume a pinch of JavaScript.
Rails 7 Hotwire is the default front-end framework shipped with Rails 7 after it was launched. It is used to represent HTML over the wire in the Rails application. Previously, we used to add a hotwire-rails gem in our gem file and then run rails hotwire: install. However, with the introduction of Rails 7, the gem got deprecated. Now, we use turbo-rails and stimulus rails directly, which work as Hotwire’s SPA-like page accelerator and Hotwire’s modest JavaScript framework.
Hotwire is a package of different frameworks that help to build applications. It simplifies the developer’s work for writing web pages without the need to write JavaScript, and instead sending HTML code over the wire.
Introduction to The Hotwire Framework:
It uses simplified techniques to build web applications while decreasing the usage of JavaScript in the application. Turbo offers numerous handling methods for the HTML data sent over the wire and displaying the application’s data without actually loading the entire page. It helps to maintain the simplicity of web applications without destroying the single-page application experience by using the below techniques:
Turbo Frames: Turbo Frames help to load the different sections of our markup without any dependency as it divides the page into different contexts separately called frames and updates these frames individually.
Turbo Drive: Every link doesn’t have to make the entire page reload when clicked. Only the HTML contained within the tag will be displayed.
Turbo Streams: To add real-time features to the application, this technique is used. It helps to bring real-time data to the application using CRUD actions.
It represents the JavaScript framework, which is required when JS is a requirement in the application. The interaction with the HTML is possible with the help of a stimulus, as the controllers that help those interactions are written by a stimulus.
Not much information is available about Strada as it has not been officially released yet. However, it works with native applications, and by using HTML bridge attributes, interaction is made possible between web applications and native apps.
Simple diagrammatic representation of Hotwire Stack:
As we are implementing the Ruby on Rails Hotwire tutorial, make sure about the following installations before you can get started.
Looking for an enthusiastic team of ROR developers to shape the vision of your web project?
Contact Bacancy today and hire Ruby developers to start building your dream project!
Find the following commands to create a rails application.
mkdir ~/projects/railshotwire
cd ~/projects/railshotwire
echo "source 'https://rubygems.org'" > Gemfile
echo "gem 'rails', '~> 7.0.0'" >> Gemfile
bundle install
bundle exec rails new . --force -d=postgresql
Now create some files for the project, up till now no usage of Rails Hotwire can be seen.
Fire the following command in your terminal.
echo "class HomeController < ApplicationController" > app/controllers/home_controller.rb
echo "end" >> app/controllers/home_controller.rb
echo "class OtherController < ApplicationController" > app/controllers/other_controller.rb
echo "end" >> app/controllers/home_controller.rb
echo "Rails.application.routes.draw do" > config/routes.rb
echo ' get "home/index"' >> config/routes.rb
echo ' get "other/index"' >> config/routes.rb
echo ' root to: "home#index"' >> config/routes.rb
echo 'end' >> config/routes.rb
mkdir app/views/home
echo '<h1>This is Rails Hotwire homepage</h1>' > app/views/home/index.html.erb
echo '<div><%= link_to "Enter to other page", other_index_path %></div>' >> app/views/home/index.html.erb
mkdir app/views/other
echo '<h1>This is Another page</h1>' > app/views/other/index.html.erb
echo '<div><%= link_to "Enter to home page", root_path %></div>' >> app/views/other/index.html.erb
bin/rails db:create
bin/rails db:migrate
Additionally, you can clone the code and browse through the project. Here’s the source code of the repository: Rails 7 Hotwire application
Now, let’s see how Hotwire Rails can work its magic with various Turbo techniques.
Go to your localhost:3000 on your web browser and right-click on the Inspect and open a Network tab of the DevTools of the browser.
Now click on go to another page link that appears on the home page to redirect from the home page to another page. In our Network tab, we can see that this action of navigation is achieved via XHR. It appears only the part inside HTML is reloaded, here neither the CSS is reloaded nor the JS is reloaded when the navigation action is performed.
By performing this action we can see that Turbo Drive helps to represent the HTML response without loading the full page and only follows redirect and reindeer HTML responses which helps to make the application faster to access.
This technique helps to divide the current page into different sections called frames that can be updated separately independently when new data is added from the server.
Below we discuss the different use cases of Turbo frame like inline edition, sorting, searching, and filtering of data.
Let’s perform some practical actions to see the example of these use cases.
Make changes in the app/controllers/home_controller.rb file
#CODE
class HomeController < ApplicationController
def turbo_frame_form
end
def turbo_frame submit
extracted_anynumber = params[:any][:anynumber]
render :turbo_frame_form, status: :ok, locals: {anynumber: extracted_anynumber, comment: 'turbo_frame_submit ok' }
end
end
Add app/views/home/turbo_frame_form.html.erb file to the application and add this content inside the file.
#CODE
<section>
<%= turbo_frame_tag 'anyframe' do %>
<div>
<h2>Frame view</h2>
<%= form_with scope: :any, url: turbo_frame_submit_path, local: true do |form| %>
<%= form.label :anynumber, 'Type an integer (odd or even)', 'class' => 'my-0 d-inline' %>
<%= form.text_field :anynumber, type: 'number', 'required' => 'true', 'value' => "#{local_assigns[:anynumber] || 0}", 'aria-describedby' => 'anynumber' %>
<%= form.submit 'Submit this number', 'id' => 'submit-number' %>
<% end %>
</div>
<div>
<h2>Data of the view</h2>
<pre style="font-size: .7rem;"><%= JSON.pretty_generate(local_assigns) %></pre>
</div>
<% end %>
</section>
Make some adjustments in routes.rb
#CODE
Rails.application.routes.draw do
get 'home/index'
get 'other/index'
get '/home/turbo_frame_form' => 'home#turbo_frame_form', as: 'turbo_frame_form'
post '/home/turbo_frame_submit' => 'home#turbo_frame_submit', as: 'turbo_frame_submit'
root to: "home#index"
end
#CODE
<h1>This is Rails Hotwire home page</h1>
<div><%= link_to "Enter to other page", other_index_path %></div>
<%= turbo_frame_tag 'anyframe' do %>
<div>
<h2>Home view</h2>
<%= form_with scope: :any, url: turbo_frame_submit_path, local: true do |form| %>
<%= form.label :anynumber, 'Type an integer (odd or even)', 'class' => 'my-0 d-inline' %>
<%= form.text_field :anynumber, type: 'number', 'required' => 'true', 'value' => "#{local_assigns[:anynumber] || 0}", 'aria-describedby' => 'anynumber' %>
<%= form.submit 'Submit this number', 'id' => 'submit-number' %>
<% end %>
<div>
<% end %>
After making all the changes, restart the rails server and refresh the browser, the default view will appear on the browser.
Now in the field enter any digit, after entering the digit click on submit button, and as the submit button is clicked we can see the Turbo Frame in action in the below screen, we can observe that the frame part changed, the first title and first link didn’t move.
Turbo Streams deliver page updates over WebSocket, SSE or in response to form submissions by only using HTML and a series of CRUD-like operations, you are free to say that either
This transmit can be represented by a simple example.
#CODE
class OtherController < ApplicationController
def post_something
respond_to do |format|
format.turbo_stream { }
end
end
end
Add the below line in routes.rb file of the application
#CODE
post '/other/post_something' => 'other#post_something', as: 'post_something'
Superb! Rails will now attempt to locate the app/views/other/post_something.turbo_stream.erb template at any moment the ‘/other/post_something’ endpoint is reached.
For this, we need to add app/views/other/post_something.turbo_stream.erb template in the rails application.
#CODE
<turbo-stream action="append" target="messages">
<template>
<div id="message_1">This changes the existing message!</div>
</template>
</turbo-stream>
This states that the response will try to append the template of the turbo frame with ID “messages”.
Now change the index.html.erb file in app/views/other paths with the below content.
#CODE
<h1>This is Another page</h1>
<div><%= link_to "Enter to home page", root_path %></div>
<div style="margin-top: 3rem;">
<%= form_with scope: :any, url: post_something_path do |form| %>
<%= form.submit 'Post any message %>
<% end %>
<turbo-frame id="messages">
<div>An empty message</div>
</turbo-frame>
</div>
This action shows that after submitting the response, the Turbo Streams help the developer to append the message, without reloading the page.
Another use case we can test is that rather than appending the message, the developer replaces the message. For that, we need to change the content of app/views/other/post_something.turbo_stream.erb template file and change the value of the action attribute from append to replace and check the changes in the browser.
#CODE
<turbo-stream action="replace" target="messages">
<template>
<div id="message_1">This changes the existing message!</div>
</template>
</turbo-stream>
When we click on Post any message button, the message that appear below that button will get replaced with the message that is mentioned in the app/views/other/post_something.turbo_stream.erb template
There are some cases in an application where JS is needed, therefore to cover those scenarios we require Hotwire JS tool. Hotwire has a JS tool because in some scenarios Turbo-* tools are not sufficient. But as we know that Hotwire is used to reduce the usage of JS in an application, Stimulus considers HTML as the single source of truth. Consider the case where we have to give elements on a page some JavaScript attributes, such as data controller, data-action, and data target. For that, a stimulus controller that can access elements and receive events based on those characteristics will be created.
Make a change in app/views/other/index.html.erb template file in rails application
#CODE
<h1>This is Another page</h1>
<div><%= link_to "Enter to home page", root_path %></div>
<div style="margin-top: 2rem;">
<%= form_with scope: :any, url: post_something_path do |form| %>
<%= form.submit 'Post something' %>
<% end %>
<turbo-frame id="messages">
<div>An empty message</div>
</turbo-frame>
</div>
<div style="margin-top: 2rem;">
<h2>Stimulus</h2>
<div data-controller="hello">
<input data-hello-target="name" type="text">
<button data-action="click->hello#greet">
Greet
</button>
<span data-hello-target="output">
</span>
</div>
</div>
Make changes in the hello_controller.js in path app/JavaScript/controllers and add a stimulus controller in the file, which helps to bring the HTML into life.
#CODE
import { Controller } from "@hotwired/stimulus"
export default class extends Controller {
static targets = [ "name", "output" ]
greet() {
this.outputTarget.textContent =
`Hello, ${this.nameTarget.value}!`
}
}
Go to your browser after making the changes in the code and click on Enter to other page link which will navigate to the localhost:3000/other/index page there you can see the changes implemented by the stimulus controller that is designed to augment your HTML with just enough behavior to make it more responsive.
With just a little bit of work, Turbo and Stimulus together offer a complete answer for applications that are quick and compelling.
Using Rails 7 Hotwire helps to load the pages at a faster speed and allows you to render templates on the server, where you have access to your whole domain model. It is a productive development experience in ROR, without compromising any of the speed or responsiveness associated with SPA.
We hope you were satisfied with our Rails Hotwire tutorial. Write to us at service@bacancy.com for any query that you want to resolve, or if you want us to share a tutorial on your query.
For more such solutions on RoR, check out our Ruby on Rails Tutorials. We will always strive to amaze you and cater to your needs.
Original article source at: https://www.bacancytechnology.com/
1595402640
I wonder if Microsoft knew what it had on its hands back in 2015 when it created Visual Studio Code, the little code editor that could.
Did the VS Code team even envision the free, open source code editor could, in less than four years after its debut, become the No. 1 development tool in a major development survey, eclipsing its namesake IDE that can cost some $6,000 per year?
That’s what happened, and the success of VS Code – along with the evolution of the open source, cross-platform .NET Core – provides the signature theme of 2018 in the Microsoft developer ecosystem. This was the year Microsoft finally shook off the last vestiges of its perception as a proprietary, monolithic corporate predator, transforming like a chrysalis to emerge as an open source champion.
As unlikely as it would seem, providing a free, performant and versatile code editor was probably a requirement for Microsoft to complete its journey to open source advocate. Leading the charge to .NET Core with a huge (some would say “bloated”), sometimes-costly (there is a free edition) enterprisey IDE that just runs on Windows (yes, there is a Mac version, but it’s problematic) just doesn’t work.
VS Code, though, fits the bill.
That was confirmed this year when Stack Overflow – known for its huge programming Q&A site – released its comprehensive developer survey, which polled more than 100,000 developers in 183 countries.
No. 1 on Stack Overflow **(source: Stack Overflow).**
“Visual Studio Code just edged out Visual Studio as the most popular developer environment tool across the board,” said Stack Overflow, which divided that “board” into four planks: All Respondents, Web Developers, Mobile Developers and Sysadmin/DevOps.
VS Code was No. 1 in the first two categories and No. 2 in the last two, finishing behind Android Studio in Mobile and Vim for Sysadmin/DevOps. In the previous year’s SO survey, VS Code placed no higher than fifth place among all segments.
While it only beat out Visual Studio IDE by .6 percentage points in the SO survey, its ascension was foreshadowed some six months earlier in yet another huge developer survey conducted by yet another huge developer platform.
This time, GitHub in its “State of the Octoverse” report saw VS Code repeat as the No. 1 open source project when measured by contributor count, which clocked in at about 15,000.
The 2018 GitHub report showed VS Code repeat in popularity (now up to some 19,000 contributors) and also – probably not coincidentally – noted that Microsoft was the organization with the most employees contributing to open source, with 7,700 contributors, well ahead of No. 2 Google at 5,500 contributors.
Editor Usage Rates **(source: Triplebyte).**
And much newer research has further confirmed VS Code is on the rise, as technical recruiting specialist Triplebyte just recently noticed a huge upsurge in the code editor’s use among its developer job candidates conducting rigorous interviews.
“Visual Studio Code is on the rise,” Triplebyte said. “Over the past year, it has become the most popular editor across the board, and it’s gaining ground every month.”
While VS Code’s popularity is well-known and well-charted elsewhere, this Triplebyte research certainly provided insight into the rapid hike in popularity.
For example, in discussing the above graphic, the firm said, “The first thing that jumps out from this graph is the prominence of Visual Studio Code. With 17 percent of the pie, VS Code was the editor used by the plurality of Triplebyte candidates last year. This was a surprise to me for two reasons. First, VS Code is a relatively new product from Microsoft, and, second, last year it didn’t even appear on our charts – its share was small enough to fall into the ‘other’ bucket.”
#visual studio code #visual studio #coding
1597518000
Não é todo programador que gosta de compartilhar o seu trabalho ou até mesmo receber feedbacks de como o seu código foi escrito, mas o Code Review é cada vez mais comum em empresas do mundo todo.
Conheça uma extensão para Visual Studio Code e comece a trabalhar com Code Review em seu próximo projeto. Essa é a sua chance de saber COMO USAR e trabalhar com Code Review no Visual Studio Code.
#visual studio code #code review #visual studio #code
1596975120
Join Mads Kristensen from the Visual Studio team each week as he builds extensions for Visual Studio live!
#visual studio code #visual studio #code #microsoft #visual studio extensions
1595417520
Node or PHP?
Headless or traditional CMS?
React or Vue?
VS Code or Sublime?
Different projects require different tools. Developers must pick the right ones, which is no small task in this fast-paced environment.
And your first pick—choosing a code editor—is crucial.
In this post, I want to explore two of them, Visual Studio Code and Sublime Text, and help you make that decision.
Why these two, you ask? Because:
I’ll present both of them, and compare their advantages & limitations.
I’ll then dedicate a full section to JavaScript development on VS Code. Frontend developers, you might want to stick around for that last one!
VS Code was released in 2015 by Microsoft. It’s cross-platform, open-source, and completely free.
Don’t let its young age fool you though: it grew crazy fast and already has a broad extensions & plugins community.
It’s the code editor that our development team uses the most for day-to-day tasks. But I promise to stay impartial. ;)
When asking why devs choose VS Code as their primary editor, the same characteristics often come up: lean, customizable, light & fast.
Some key features also helped make it so popular. First, its super smart IntelliSense provides the best autocomplete discovery for a bunch of languages.
Its support for debugging (mainly for Node.js & JavaScript, which I’ll come back to later) also eases a lot of pains developers might experience otherwise.
If you haven’t heard, .NET is a big part of our development stack at Snipcart. And even though the old Visual Studio might still be better for older .NET solutions, VS Code is an excellent match for .NET Core.
Without spoiling too much of the end of this post, VS Code is also a very viable match for JavaScript & frontend development…
All in all, Visual Studio Code is a great tool. Our team recommends it to any developers who like to fine-tune their code environment.
Its large library of extensions can be found here, in the Visual Studio Marketplace.
Sublime is a more mature code editor, already over a decade old. It was released in 2007 by Jon Skinner, a former Google engineer. It presents itself as a a sophisticated text editor for code, markup and prose.
Also cross-platform, Sublime isn’t free, at a price of 80$/license.
Much like VS Code, Sublime gets lots of praises when it comes to performance and customization.
Some say it’s the fastest text editor for writing code. Not only in general performance but also to run fast searches across any number of files. It reaches this level of performance by being very, very lightweight.
Overall, Sublime is a great jack-of-all-trades platform that is sure to please any developer with its speed and stability.
All of its extensions are listed here, in Package Control.
It’s hard to pinpoint a clear winner in this comparison.
These are both very reliable tools. You probably won’t regret your choice no matter which one you go with. Once again, this post was created to guide you through that decision.
Editor performance
On a pure speed level, Sublime is hard to beat. The main issue with VS Code when it comes to performance is that it’s based on the Electron framework which uses an instance of Chromium. This makes the app slower at launch.
This is an issue only if you really care about these few seconds of startup load time. It looks like most developers can live with it, as VS Code is fast enough the rest of the time.
Also, Sublime’s performance seems to get way more impacted by bigger projects. On the other hand, VS Code scales well in that regard.
If you’re used to working with Atom though, both will feel like a significant improvement for performance!
Sublime, however, takes the win when it comes to performing quick searches. When you open a project, it automatically runs a “symbol analysis,” spotting keywords in your code. With a simple command, you can easily find class names and methods within your files. You’ll be able to do the same in VS Code, but only with a few languages supported out-of-the-box.
#visual studio code #visual studio #css #coding