| 14 Apr 2022 |
|  Negative_Man joined the room. | 03:16:12 |
|  dpo joined the room. | 04:36:58 |
|  moschroe joined the room. | 08:47:34 |
|  StyMaar changed their display name from StyMaar#1539 to StyMaar. | 08:56:24 |
| StyMaar | Isn't the blur caused by scaling issues (on the druid/winit side)? I'm not a gfx expert in any way, but I have trouble understanding how this could be caused by wgpu | 08:56:25 |
 ghishadow#6592 | it is text rendering issue, here is thread where dzhou explained why he is dropping wgpu https://discord.com/channels/946858761413328946/948880865373609994/961175157332906004 , Opengl will live for long time with Zink | 09:36:04 |
|  abbe#8165 joined the room. | 10:45:32 |
| abbe#8165 | Hey, I just found this editor, which looks really cool. Is there DAP support currently or is it planned. | 10:45:33 |
|  Kale joined the room. | 11:09:20 |
 dzhou121 | Thanks. DAP is on the plan. | 11:20:36 |
| abbe#8165 | Amazing. Honestly an editor matching high performance(sublime), powerful(vim), but IDE-like(vim and perhaps vscode) is non-existing tbh | 11:21:27 |
| abbe#8165 | While vim does most things a real editor is favourable at times. | 11:21:50 |
| abbe#8165 | I wanted to purchase sublime but I do like the ability to do simple debugging. Essentially launch programs and put breakpoints | 11:23:20 |
| dzhou121 | I was a Vim user and tried to implement neovim GUI to make vim “morden”. But it was just too hard. | 11:24:08 |
| abbe#8165 | Yeah vim is functionally ideal but I'm not a perfect keyboard user. A real GUI editor is preferential but there are none | 11:24:39 |
| abbe#8165 | Clion and that family is powerful but slow and clunky. Vscode is ok but feels a bit slow and autocomplete is bad, in comparison to other editors | 11:27:23 |
| dzhou121 | Yeah I was using VSCode for a while. It was a bit slow for me. | 11:31:52 |
| abbe#8165 | I am using neovim at the moment but for languages like Java you need a real workspace | 11:32:31 |
|  martini joined the room. | 16:45:54 |
|  reese joined the room. | 19:16:40 |
| reese | hello | 19:18:53 |
| reese | i just tried out lapce and it looks pretty cool so far! i'm curious, what's the current state of syntax highlighting support? i'd love to help out with writing or adding some definitions for common languages. | 19:27:43 |
| reese | also i'm currently a sublime user. i used atom for several years before that and it's just so bloated and slow as a result of being based on electron. i also tried vscode once i got fed up with it but it had the same problems for me. i use micro or nano in a terminal if i need to but i do prefer a gui and standard keybindings. | 19:32:08 |
| reese | * also i'm currently a sublime user. i used atom for several years before that and it's just so bloated and slow as a result of being based on electron. i also tried vscode once i got fed up with atom but it had the same problems for me. i use micro or nano in a terminal if i need to but i do prefer a gui and standard keybindings. | 19:50:14 |
|  Blessing changed their display name from Blessing to Blessing#2776. | 21:47:26 |
| Blessing changed their display name from Blessing#2776 to Blessing. | 21:47:27 |
| Blessing | I guess you can refer to their github | 21:47:28 |
| Blessing | * I guess you can refer to their github repo | 21:47:33 |
 Yakei | Hey! Syntax highlighting support is done using tree-sitter. as of now, the list is not as extensive as sublime or atom, but it's very easy to add some new highlighting: as long as there is a tree sitter written for a language, it's a matter of a few lines to reference it in the code. | 21:53:33 |
| Yakei | you have plenty of merged PR with tree sitter that you can look at if you want | 21:53:56 |
