teleren/devto huggingface dataset:
Tips for Collaborating Effectively with a Mobile App Development Team
Tags: mobile, devops, developer
Published: 2024-04-20 06:12:43

Collaborating with a mobile app development team can be a rewarding experience if done right. Effective communication, mutual respect, and clear goals are essential to a successful partnership. Here are some tips for better collaboration with your mobile app development team:

Clear communication: Keep the lines of communication open at all times. Openly discuss your thoughts, expectations, and ideas with the team. Regular updates and feedback can help keep everyone on the same page.

Set clear objectives: Define clear goals and objectives for your mobile app business. This will help the development team understand their expectations and work towards achieving those goals more effectively.

Rely on experts: Rely on the expertise of your mobile app development team. They have the knowledge and experience to make informed decisions and recommendations that can benefit your project.

Be open to feedback: Listen to feedback and suggestions from the development team. They can give you valuable insights and perspectives that you may not have considered.

Honors deadline: Agreed honors deadlines and highlights. Timely delivery is crucial for any successful mobile app project.

Stay flexible: Be open to changes in the development process. Sometimes unexpected challenges arise, and adjustments can help them cope.

Provide resources: Ensure that the development team has access to all required resources, such as design assets, documentation, and necessary tools, to ensure smooth development.

Regularly track progress: Regularly monitor the progress of mobile app development and ensure that it is aligned with your expectations and goals. This will help you anticipate any potential issues and address them as soon as possible.

Remember, collaboration is a two-way street. By creating a collaborative and respectful environment, you can work effectively with your mobile app development team to create a successful and impactful mobile app.

Consider partnering with AnA Info for high-quality mobile app development services. With their expertise and dedication to excellence, they can help bring your app idea to life. Visit the AnA Info website to learn more about their services and how they can help you along your mobile app development journey.
Thể thao 24 giờ
Tags: thethao24gio
Published: 2024-04-20 06:10:12

Thể thao 24 giờ https://thethao24gio.com/ Thethao24gio - cập nhật các thông tin thể thao HOT trong 24 giờ qua với đa dạng loại hình : bóng đá, bóng rổ, bóng chày, bóng chuyền, đua xe, golf, e-sport... 
Địa chỉ : Số 8 mễ trì hạ, mễ trì, nam từ liêm, hà nội  

Email : thethao24gio.com@gmail.com

Website : https://thethao24gio.com

Facebook : https://www.facebook.com/thethao24giochamcom

Twitter : https://twitter.com/thethao24gio_

Youtube: https://www.youtube.com/@thethao24gio_com

Pinterest : https://www.pinterest.co.kr/thethao24gio
Fast Burn Keto - Extreme Thermogenic Weight reduction Supplement?
Tags: fastburnketo
Published: 2024-04-20 06:09:35

The weight reduction process isn't just difficult, however it is tedious too. To shed pounds an adequate measure of weight, you really want to go through hours at the exercise center, plan and spotlight on a tight eating routine arrangement, and screen what you eat.

Fortunately nowadays, you don't have to invest all of that energy to encounter results. All you truly need is a solid wellness normal, a fair eating regimen, and an excellent weight reduction supplement that you can depend on.

That being said, this survey might want to acquaint you with [Fast Burn Keto](https://www.fastburnketo.net/
). With this enhancement, you can thin down and meet your weight reduction objectives. Here is all that you really want to be aware of Fast Burn Keto preceding you purchase:


What is Fast Burn Keto?
Fast Burn Keto is another weight reduction supplement available that empowers you to thin down and to meet your weight reduction objectives. The item includes unadulterated Fast Burn Keto berry, a super organic product that has a huge number of medical advantages.

By adding this enhancement to your day to day wellbeing schedule, your body will actually want to consume fat all the more successfully, your digestion will increment, and you'll encounter every one of the advantages to be had from an item that is plentiful in cell reinforcements, nutrients, and minerals.

Until this point in time, Fast Burn Keto has helped endless of people arrive at their weight reduction and wellbeing objectives. Presently, you also can encounter similar strong outcomes when you add this item to your everyday practice.

[https://www.fastburnketo.net/
](https://www.fastburnketo.net/
)[https://twitter.com/fastburn_keto
](https://twitter.com/fastburn_keto
)[https://www.instagram.com/fastburnketo/
](https://www.instagram.com/fastburnketo/
)[https://www.pinterest.com/fastburnketo_/
](https://www.pinterest.com/fastburnketo_/
)[https://www.facebook.com/profile.php?id=61558235593218
](https://www.facebook.com/profile.php?id=61558235593218
)[https://www.youtube.com/@FastBurnKeto](https://www.youtube.com/@FastBurnKeto)
Trust no one: don't trust debug message
Published: 2024-04-20 06:02:05

Did you know that even a machine can lie to you? The only difference is that it's human that makes the machine lie. Not like long time ago, most of the time you can easily find a good explanation for any error or exception you encounter when you code. However, not all messages are of the same weight.

When I was in my last job, I learned it (a bit) hard way.
[Don't trust message your Javascript console emits.]
While others were trying to find the root cause based on the Javascript console, I intentionally ignored it, since it didn't make sense at all in machine language level. Anyway, the message was  written by a human, so the console had to lie as the program's exception handler says.

Well, sometimes, you have to see beyond the scene, and read between lines.
아무도 믿지 말라: 디버그 메시지도 믿지 말고
Published: 2024-04-20 05:59:50

기계도 거짓말을 합니다. 단지 차이점이라면, 그 거짓말을 시키는건 사람이라는 거죠. 예전과는 다르게 요즘은 대부분의 경우 뭔가 오류나 예외가 발생하면 그 내용을 친절하게 설명해 줍니다. 하지만, 모든 메시지가 다 똑같은 무게를 갖고 있는 것은 아닙니다.

전 직장에서 가장 크게 배운 것이 한 가지 있습니다.
[자바스크립트 콘솔이 내뱉는 메시지를 믿지 말라]
다른 모든 사람들이 메시지만 보고 허둥댈때 저는 그 메시지를 무시하고 직접 파고들어 원인을 찾아낸 경험이 있었습니다. 아무리 봐도 기계어 수준에서는 말이 안 되는 화면이었거든요. 화면에 표시되는 메시지도 사람이 직접 쓴 것이므로, 그 메시지를 쓴 사람이 내용을 잘못 쓰거나 메시지가 나오는 맥락을 잘못 이해하면 컴퓨터는 거짓말을 할 수밖에 없습니다.

뭐, 가끔은 화면 위의 연출 뒤쪽도 봐야 되고, 행간도 읽어야 하는 법이죠.
My Journey to Creating My First Project: TechTribe Pro by Juan Jose
Tags: webdev, fullstack, sqlserver, react
Published: 2024-04-20 05:56:07

Hi dev.to community! 👋 I'm Juan Jose, a newcomer in the coding world, and I'm diving into the exciting realm of coding. I'm thrilled to share with you my plans to embark on my first coding project!

I'm excited to introduce my project, TechTribe Pro. 🚀 Customers will be able to submit tickets online through our user-friendly portal, providing details about their IT issues, device information, and desired services.

We will offer a wide range of IT support and repair services, including hardware repairs, software installations, virus removal, data recovery, network setup, and device optimization. Each service is categorized to facilitate efficient handling and prioritization. 💻🔧

Planning and Preparation:
I've spent some time planning and organizing my project to ensure its success. Here's how I've approached the planning process: I've broken down the project into manageable tasks and created a [Trello board](https://trello.com/b/zlB7qc1S/techticketing-pro) to track my progress. Additionally, I'm using the Agile methodology to stay flexible and adapt to any changes along the way. 📝📅

Technologies:
For my project, TechTribe Pro, I'll be using React.js for the front end and building a Web API with .NET SQL for the backend. I chose these technologies because React.js provides a fast and efficient way to create dynamic user interfaces, while .NET SQL offers robust database management capabilities, ensuring scalability and reliability for my project. 💡⚙️

Challenges and Expectations:
While I'm excited about this project, I anticipate facing some challenges along the way. One challenge I expect to encounter is integrating the front end with the backend seamlessly. To overcome this, I'll be dedicating time to thoroughly understanding the RESTful API architecture and how to effectively communicate between the client and server. My expectation for this project is to gain valuable experience in full-stack development and deliver a functional application that meets the needs of its users. 🤔🎯

Timeline:
I've outlined a rough timeline for TechTribe Pro, with the goal of starting development on April 22, 2024, and aiming to have a minimum viable product (MVP) ready for testing by May 6th, 2024. I'll be regularly updating my progress on dev.to and seeking feedback from the community to ensure I stay on track and deliver a quality product on time. 🚧📆

I invite you all to join me on this journey! Whether you're a seasoned developer or just starting out, your insights and feedback are invaluable to me. [Check out the GitHub Repository here](https://github.com/juan-alcalde/TechTribe-Pro). Feel free to share your own experiences, offer advice, and provide support as I work on TechTribe Pro. 🎉🤝 Together, we can make this project a success!
std::move = std::optional이 출동할 때
Tags: cpp
Published: 2024-04-20 05:54:30

이전 블로그에서 가져온 글입니다:
https://codenested.blogspot.com/2023/01/stdmove-stdoptional.html
___
최근 Rust를 살펴볼 기회가 있었습니다. Rust는 function이 결과를 반환할때 `std::option`이라는걸 사용해서 정상이면 A 클래스를, 비정상이면 B 클래스를 반환하는 형태를 취하고 있더군요.

그래서...... 혹시나 해서 찾아봤더니, C++에도 `std::optional`이 있는 것을 발견했습니다. 다만 대부분의 사용자들은 `std::optional`을 왜 쓰느냐는 입장이었습니다. 우리에겐 (밉고도 고운) `nullptr`이 있는데 뭐하러 저런걸 쓰느냐...... 하는 거였습니다. C++ Committee의 입장은 실수를 줄이기 위해서라고 하던데, 그렇다면 대체 무슨 실수가 나올 수 있을까요?

우선, 다음의 코드를 살펴봅시다.
```cpp
struct Insider {
    /* whatever great data structure */
};

struct anti_memory_leak {
    Insider *insider=nullptr;
    ~anti_memory_leak() {
        if(insider) delete insider;
    }
};
```
확실히, 이 코드는 별 특이사항이 없어 보입니다. Insider는 쓰일 때도 있고 안 쓰일때도 있어서 필요한 경우에만 heap에서 생성하도록 해 두었습니다. anti_memory_leak이 삭제될 경우 Insider 객체가 존재하면 같이 지우도록 해서 메모리 누수 방지도 해 두었습니다. 우리는 `std::optional`이 없어도 아무런 문제가 없음을 증명했습니다.

...... 과연 그럴까요?

다음의 코드를 봅시다.
```cpp
void doSomethingGreat()
{
    anti_memory_leak object1;
    object1.insider=new Insider();

    std::vector<anti_memory_leak> vector1;
    vector1.push_back(std::move(object1));
    vector1.back().insider->value1=20; // CRASH!
}
``` 
이 코드는 맨 마지막줄에서 프로그램이 터지는 결과를 가져옵니다. 왜 그럴까요? 이유는 바로 윗줄에 있습니다. `vector1.push_back()`을 호출할 경우, `std::move()`를 쓴다고 하더라도 object1은 파괴 후 재생성됩니다. 이 때 anti_memory_leak의 파괴자가 호출되고, 파괴자는 insider를 heap에서 제거합니다. 뒤집어서 말하면, `vector1.back().insider`는 dangling pointer가 되어버리는 셈이죠. 아울러 유감스럽지만, `push_back()`이 아니라 `emplace_back()`을 사용하더라도 동작은 마찬가지입니다. 어쨌든 터지는 것은 매한가지 되겠습니다.

바로 이 때가 `std::optional`이 출동할 차례입니다. `std::optional`을 사용하여 객체를 선언하면 일단 메모리는 사용되지 않은 채로 초기화되고, 추가 메모리는 실제로 해당 객체를 선언할 때 사용을 시작합니다. 물론 객체 생성에 따른 overhead가 좀 더 있긴 합니다만, 사실 그건 유사한(?) 역할을 수행하는 `std::shared_ptr` 같은 클래스도 마찬가지지요. raw pointer가 있지만 해당 heap 영역을 좀 더 안전하게 사용하기 위해서 운영의 일부를 자동화하여 개발자가 자칫 놓칠 수 있는 메모리 관리상의 문제점들(메모리 누수와 dangling pointer 모두)을 쉽게 해결하고자 하는 것입니다.

위의 코드를 std::optional을 사용하여 다시 작성한다면 이렇게 작성할 수 있겠습니다.
```cpp
struct Insider {
    int value1;
    /* whatever great data structure */
};

struct anti_memory_leak {
    std::optional<Insider> insider;
    ~anti_memory_leak() {
        if(insider) delete insider;
    }
};

void doSomethingGreat()
{
    anti_memory_leak object1;
    object1.insider=Insider();

    std::vector<anti_memory_leak> vector1;
    vector1.push_back(std::move(object1));
    vector1.back().insider.value1=20; // OK
}
```
사실 객체를 다루는 코드의 흐름이 단순하다면 크게 문제가 없겠지만, 멀티스레딩이라던가, 아니면 코드가 어떤 식으로든 복잡해지게 되면 분명히 나도 모르게 메모리를 해제하게 되거나, 내지는 해제해야 할 때 못하는 경우가 생겨나게 됩니다. std::optional은 이런 경우에 대비한 일종의 보험이라 하겠습니다. 보험료를 내는 사람들은 (뭐 좀 아깝긴 하지만) 그래도 만일의 경우에 대비해서 보험료를 내는 거잖아요? `std::optional`도 마찬가지라고 봅니다.
Vim vs. Neovim: it's yet immature
Tags: vim
Published: 2024-04-20 05:50:02

A post from my old blog:
https://codenested.blogspot.com/2023/06/vim-vs-neovim-its-yet-immature.html
___
I had a chance to try Neovim, which is quite a hot potato among Vim users. As far as I know, Neovim is started as a fork of Vim to include some features rejected by Vim maintainers. What I know about Neovim is only two: they adopted Lua as their script language along with VimScript, and LSP client is included(after v0.4).

I was really not satisfied with LSP support from Vim, so I was curious about how Neovim native LSP works. Conclusion? Well...... Before jumping into LSP, it looks like their big file management is still living the era of Vim 7. The memory consumption of Vim 9 and Neovim 0.9 are quite similar, but while in Vim you could easily navigate from here to there without any delay from Vim 8, Neovim showed quite formiddable delay when I tried to jump from the start to end at once. Also, the initial loading was a bit slow....... Though others are unanimously saying that "it's GREAT!", for me it lacks some basics as a text editor. Also, Windows installer was a bit premature compared with vim-win32-installer.

Though LSP is important for me too, but my job frequently requires processing of multi-GB size text files, I think I'll reside on Vim for some time being.

**P.S.1: My Main Development Environment**
For your reference, I use Visual Studio Code as my main development environment. Vim is mainly used to edit some texts.

**P.S.2: About Vim's LSP Plugins**
Well, for me, [CoC](https://github.com/neoclide/coc.nvim), the final boss(?), is isolating itself outside Vim ecosystem(if I have to run Node.js inside Vim, then I'd use Visual Studio Code instead), [vim-lsp](https://github.com/prabirshrestha/vim-lsp) lacks support on how to show the diagnosis results, and [ALE](https://github.com/dense-analysis/ale) doesn't show function signatures and code formatting is not supported....... Everything loses at least one core value from their stuff.

And today, I found this: https://github.com/yegappan/lsp
https://github.com/yegappan/lsp
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/q5cldwz6qxelrqm871vm.png)

You've got to make your hands a bit dirty to configure(even you've got to register your LSP servers manually), but anyway it's editing some text files(:P). And with propre configuration it provides useful information as you see in the above screenshot. And one more thing: this is developed with Vim9Script - in other words, it doesn't work in Neovim.

**P.S.3: Vim vs. Neovim - a Bridge You Can't Turn Back**
While Neovim concentrates on Lua Vim made Vim9script, and Neovim announced they won't support Vim9script. I think this will be the marker of separation between these two projects. Personally it reminds me of the end of "full compatiblity" between MySQL 8 and MariaDB 10 due to differences in JSON support. The difference? In MySQL / MariaDB case the fork, MariaDB, shows better performance than MySQL, while in Vim / Neovim case the original, Vim, is better(at least to me).
급할수록 돌아가라
Published: 2024-04-20 05:36:23

이전 블로그에서 가져온 글입니다:
https://codenested.blogspot.com/2024/02/blog-post.html
___
간혹 옛 성현들의 말씀 중에 틀린게 없다는걸 새삼 실감할 때가 있습니다. 최근에 그런걸 다시 한 번 느꼈는데...... 급할수록 돌아가라 하셔서 돌아갔더니만 궁극적으로 시간을 더 절약하게 되더군요.

상황은 대충 이렇습니다. 특정 데이터를 추출하는 새로운 기능을 만들어야 하는데,  겉으로 보기엔 간단하지만 실제로는 간단하지 않겠다는 생각이 들었습니다. 하나의 raw data에서 요약본과 메인 데이터 두 개를 추출해야 하는데, 반복문을 한 번만 돌리면 전체적으로는 수행이 더 빠르겠다는 생각이 들더군요. 하지만 기존의 데이터 저장 체계와 맞물려서 생각해보면 이걸 두 개의 스레드로 분리해야 할 수밖에 없는 상황이었는데...... 하루면 끝낼 일을, 일부러 사흘 정도 딴짓(?)을 하면서 시간을 질질 끌어보니 답이 나왔습니다. loop를 한 개로 놓고 데이터를 subsection 형태로 나누면 어떻게든 되곘더군요.

제가 평소 업무중 중요시하는 것 중 하나가 부화 효과입니다. 어려운 문제가 주어졌을 때 그 문제에 무작정 집중하지 말고, 그 문제와 전혀 관련없는 다른 일을 수행하다가 원래의 문제로 돌아오면 기존에는 보지 못했던 새로운 지평이 보인다는, 무려 심리학 실험을 통해 검증된 효과입니다. 왜 이러한 효과가 발생하느냐에 대해서는 아직 학계에서 갑론을박 중인 것으로 알고 있습니다만, 블랙박스의 내부 구조를 밝히는 것은 학계의 영역이고, 전 그저 쓰기만 하면 될 뿐이죠. :D

소소합니다만, **나는 틀리지 않았어!** 하고 다시 한 번 확인하게 되는, 강화 요인 중 하나가 되었기에 끼적여봅니다.
Vim vs. Neovim: 아직은 좀 설익은 과일
Tags: vim
Published: 2024-04-20 05:48:27

이전 블로그에서 가져온 글입니다:
https://codenested.blogspot.com/2023/06/vim-vs-neovim.html
___
최근 몇년간 Vim 사용자들에게 최고의 화두였던 Neovim을 잠깐 만져봤습니다. 제가 듣기로 Neovim은 Vim에서 이것좀 구현해주세요 했다가 "야 Vim은 지금 이 상태로 완전하거든?" 이란 말과 함께 퇴짜맞은 기능들을 넣은 fork로 출발한 프로젝트로 알고 있습니다. 주요한 특징이라면 스크립트 언어로 Lua를 채용했다거나, LSP를 내장했다거나(v0.4 이후) 정도로군요.

그러잖아도 Vim의 LSP 지원이 다들 영 마음에 안 들어서 좀 고민하던 차에, 내장 LSP가 어떻게 생겨먹었나 궁금해서 Neovim을 써봤습니다. 결론은 뭐....... LSP는 고사하고 대용량 파일 처리가 Vim 7 시절 그대로인 것 같더군요. 메모리 사용량은 Neovim 0.9나 Vim 9이나 비슷한데, Vim 8은 큰 파일도 날라댕기면서(......) 왔다갔다 하는게 가능한 반면 Neovim은 파일 처음에서 끝까지 가려면 한참을 기다려야 하더군요. 초기 로딩도 슬쩍 느리고...... 뭐랄까요. 써본 사람들은 다들 좋다 좋다 하는데 제게는 기본기가 좀 어설프다는 느낌이었습니다. Windows용 설치파일도 Vim Win32 Installer에 비하면 여러가지로 부족한 점이 많아 보였고요.

LSP도 LSP지만, 전 아무래도 대용량 텍스트(수 GB 이상)를 처리해야 되는 경우가 꽤 되어서, 당분간은 Vim에 계속 남아있게 될 것 같습니다.

**P.S.1: 나의 메인 개발환경**
아, 참고로 전 제 메인 개발환경으로 Visual Studio Code를 씁니다. Vim은 텍스트 편집이 주 용도에요.

**P.S.2: Vim의 LSP 플러그인 이야기**
일단 대충 끝판왕(......)인 [CoC](https://github.com/neoclide/coc.nvim)는 Vim의 ecosystem 바깥에서 따로 놀고 있고(Vim 안에서 Node.js 돌릴거면 그냥 Visual Studio Code 쓰고 말죠), [vim-lsp](https://github.com/prabirshrestha/vim-lsp)는 화면 표시 기능이 빈약하고, [ALE](https://github.com/dense-analysis/ale)는 function signature가 표시가 안 될 뿐더러 code formatting 기능이 없고....... 뭐 다들 뭔가 한가지씩 필요한게 빠진 느낌이었습니다.

그러다가 오늘 괜찮은걸 발견했습니다. 이겁니다: https://github.com/yegappan/lsp
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/q5cldwz6qxelrqm871vm.png)

설정이 좀 번거롭긴 한데(LSP 서버도 수동으로 등록해야 됩니다), 그래봐야 텍스트 파일 편집이 전부이기도 하고, 잘 만져주면 위쪽 화면처럼 표시도 해줘서 보기가 엄청 편합니다. 그리고 결정적으로....... Vim9script로 만들었더군요. 옙. Neovim에서는 못 씁니다(......).

**P.S.3: Vim vs. Neovim - 돌아올 수 없는 다리**
Neovim이 Lua를 미는 동안 Vim은 Vim9script를 만들었고, Neovim은 Vim9script를 지원하지 않겠다고 선언했지요. 저는 이게 아마 둘의 갈림길이 될 것 같습니다. 개인적으로는 JSON 지원 방식의 차이로 인해 MySQL 8과 MariaDB 10 사이의 호환성이 갈라진게 떠오르는군요. 차이라면 MySQL / MariaDB는 fork본인 MariaDB가 MySQL보다 여러모로 더 좋은 성능을 보여주는 반면 Vim / Neovim은 원본인 (최소한 제 환경에서는) Vim이 Neovim보다 더 좋아보이는 것 같군요.
The University of Albany: A Comprehensive Overview
Published: 2024-04-20 05:46:12

The University of Albany, also known as SUNY Albany, is a prestigious public research university located in Albany, New York. Established in 1844, the university has a rich history of academic excellence and is renowned for its diverse programs, accomplished faculty, and vibrant campus life. In this article, we will explore the various aspects of the University of Albany, including its history, academic programs, campus facilities, and student life.

History of the University
The University of Albany traces its origins back to the founding of the New York State Normal School in 1844. Over the years, the institution underwent several name changes and expansions, eventually becoming a comprehensive public research university. Today, the University of Albany is part of the State University of New York (SUNY) system, which is one of the largest and most respected public university systems in the United States.

Expansion and Development
In the early 20th century, the University of Albany experienced significant growth and development, with the establishment of new academic programs and the construction of modern campus facilities. The university’s commitment to academic excellence and research innovation has helped it become a leader in higher education.

Notable Alumni
The University of Albany boasts an impressive list of alumni who have achieved great success in their respective fields. From Pulitzer Prize-winning authors to renowned scientists and political leaders, the university’s alumni have made significant contributions to society.

Academic Programs
The University of Albany offers a wide range of academic programs, including undergraduate, graduate, and doctoral degrees. The university is organized into various schools and colleges, each offering unique programs tailored to students’ interests and career goals.

[READ MORE](https://mimizz.site/the-university-of-albany-a-comprehensive-overview/)
Journey to the Vim IDE, and what I learned
Published: 2024-04-20 05:44:33

A post from my old blog:
https://codenested.blogspot.com/2023/09/journey-to-vim-ide-and-what-i-learned.html
___
It's a bit late, but I learned that Bram Mooleanaar, the very developer of Vim, has passed away last month. I sincerely show my humble respect to him and his legacy, the great text editor. Rest in peace.

I'm not sure whether this is a side effect, but I spent a few days on providing IDE-like environment in Vim. Since it is the second trial the result was satisfactory, but I conclduded that I'd continue to use Visual Studio Code(VS Code) and postponed to apply the environment to the production. There are some reasons:

1. My hands got WAY TOO DIRTY on customization. Plugins collide here are there. There are some features which should be provided in plugins in Vim, while in VS Code that are embedded, and more plugins mean more breaking points, since they change the settings internally without considering the others.
1. It's most people look over, but you can use VS Code without mouse for more than 95% of actions. It's not only hot keys but also command palette with fuzzy search support. Yes. It's not the only "gift" to Vimmers motto, "we don't need mouse!"

And personally, I recognized that I tried to make Vim-IDE as similar as VS Code. It's not only behave mswin but also tab movements, file explorer, etc. If that's the case, I'd prefer to remaining in VS Code, rather than make efforts to make Vim resemble VS Code.

 In my experience, the strength of of Vim is in editing, but not insertion. For example, you have commands like da", di', dt(, or the difference of O and o. And this is the very strength of modal editor, which provides a "special mode" only for editing. Yet for me, I spend most of the time in insertion, not in editing. And in doing that, what I use most is at best autocompletion. Vim is certainly wonderful job, but considering my use case most of them are unwanted. Jumping between normal mode and insert mode and enduring the inconvenience only for features which I'd use once a month at best is quite a nonsense.

Wrapping up, I'm sure that Vim is quite a treasure, but it doesn't fit to me, like someone said in Reddit, "VS Code versus Vim is not about what's better. They're just different and appeal to different type of people."

To my dear heavy Vim users, if you read this post, please don't be angry, but think of it as a practical case of "there's nothing like a shirt that fits to all."

So everyone, happy Vimming!

**P.S:**
Yet, I'm dissatisfied with performance drops due to the limit of VS Code brought by its structure(Javascript.......). Vim is a bit better, but Vimscript is still a script also, so they're anyway about the same to me. :P

Regarding this, finding an alternative for VS Code, I found Lapce(https://lapce.dev/), which is still pre-alpha but promising. If I have a chance, let me post for this.